[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-libc-dev] SIGNAL / INTERRUPT checking

From: E. Weddington
Subject: Re: [avr-libc-dev] SIGNAL / INTERRUPT checking
Date: Fri, 27 Feb 2004 16:16:06 -0700

On 27 Feb 2004 at 17:49, Colin O'Flynn wrote:

> Hi,
> Thought of another idea.
> Search the input files for the SIGNAL() or INTERRUPT() macro, and get the 
> interrupt name (BTW are SIGNAL() and INTERRUPT() case sensitive?), then 
> search the output file for them. If it finds any it means they were not 
> converted... also search for any SIG_ for good luck (to catch anything else).
> This way for most you can get line information to report back.
> Just working on the prototype now so testing out different ideas...

Since they're #defined macros, IIRC they're case sensitive. 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]