[En-Nut-Discussion] Aspect-Oriented Programming (AOP) and Nut

Michael Gong mwgong at cs.utoronto.ca
Tue Sep 12 18:19:38 CEST 2006

Hi, Thiago,

Thanks for the information. It definitely helps.



----- Original Message ----- 
From: "Thiago A. Corrêa" <thiago.correa at gmail.com>
To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
Sent: Tuesday, September 12, 2006 12:14 PM
Subject: Re: [En-Nut-Discussion] Aspect-Oriented Programming (AOP) and Nut


  The most obvious are the trace and debug options on the nutconfig
(which translates into macros). It's possible that platform dependent
code could became platform independent code by using aspects,
althought I'm not sure. One example is the LCD display (hd7780.c) in
AVR and ARM platforms that are very much similar.

  There are also optional features that could be disabled by the use
of aspects, such as the interrupt counting, which is only usefull for
debugging as far as I know.

    Thiago A. Corrêa

On 9/12/06, Michael Gong <mwgong at cs.utoronto.ca> wrote:
> Hi, Nut community,
> I am working on Aspect-Oriented Programming (AOP) research, and wish to 
> use Nut/OS as an case study to evulate the impact of AOP on C. The tool 
> which will be used is AspectC compiler (www.aspectc.net).
> Being new to Nut, I would like to ask you for help:
>     if you are aware of any features or codes which meet any following 
> criteria, could you please let me know because they are good candidates 
> for aspects and I could try using AspectC to moduralize them so they could 
> be easily plug/unplug from Nut/OS.
>     1. any features which might be optional for the core functionality of 
> Nut/OS, like debug, trace or performance-related.
>     2. any features or code segments which you feel have to duplicate over 
> different places.
>     3. any features or code which you would like to encapsulate in a 
> class, so that it could be cleanly replaced by a future better 
> implementation.
>     4. any similiar codes which you have seen appearing a lot over 
> different locations.
> You could just send me emails, like:
>     "Hey, I think the feature of support XXX could be taken out of Nut 
> because in some situation people won't use it".
> or
>     "The following code could be remove because they are only to improve 
> performance".
> or
>     "Following code is not elegant because I have to duplicate them in 
> many places with only minor modification"
> Thanks a lot for your attention.
> Regards,
> Michael
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de

More information about the En-Nut-Discussion mailing list