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

[Michael Gong]

Hi, Matthias,

Thanks for the information. I haven't started the work and am currently 
making AspectC compiler stable (www.aspectc.net).

But I will definitely take your suggestion into consideration when doing the 
refactoring work on Nut.

Regards,

Mike

----- Original Message ----- 
From: "Matthias Ringwald" <mringwal at inf.ethz.ch>
To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
Sent: Thursday, October 26, 2006 10:45 AM
Subject: Re: [En-Nut-Discussion] Aspect-Oriented Programming (AOP) and Nut


> Hi Michael
>
> AOP in C on Nut sounds cool. :)
>
> I guess most of all pre-processor #define #ifdef #else .. constructs
> are Aspect candidates.
>
> The avr/usart driver e.g. has several options to support half-duplex,
> software flowcontrol, hw flowcontrol, cooked modes, etc..
> all of those are added with #ifdefs mostly because time in IRQ
> handlers is limited and most people prefer to optimize there.
>
> The obvious "debug" and "trace" argument for Aspects clearly applies
> to Nut/OS. There are quite some DEBUG and NUTTRACER macros which
> can even timestamp IRQs.
>
> good luck,
> matthias
>
>
> other ty
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>