[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] SIGNAL / INTERRUPT checking
From: |
Colin O'Flynn |
Subject: |
Re: [avr-libc-dev] SIGNAL / INTERRUPT checking |
Date: |
Sat, 28 Feb 2004 09:23:59 +0000 |
User-agent: |
KMail/1.5.3 |
Hi,
Yup - could do that! That should catch people who misspell the SIGNAL() and
INTERRUPT() macros as well at the time....
What sort of output does the preprocessor give you? Like is it just one big
file or what....
Regards,
-Colin
On February 27, 2004 11:15 pm, E. Weddington wrote:
> On 27 Feb 2004 at 17:53, Colin O'Flynn wrote:
> > Oh yeah, one more thing.
> >
> > How should I deal with #define'd SIG_ names? I figure the only way would
> > be to do as suggested and look up in the output for SIG_
> >
> > ie:
> > #define UART SIG_UART_0
> >
> > SIGNAL(UART)
>
> Shot in the dark:
> Maybe in the makefile, run the preprocessor on the files and look at the
> preprocessed output?
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, (continued)
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, Joerg Wunsch, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, E. Weddington, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, E. Weddington, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, Colin O'Flynn, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, Colin O'Flynn, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, E. Weddington, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, Colin O'Flynn, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, E. Weddington, 2004/02/27
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking,
Colin O'Flynn <=
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, E. Weddington, 2004/02/28
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, Clemens Buchacher, 2004/02/29
- Re: [avr-libc-dev] SIGNAL / INTERRUPT checking, Colin O'Flynn, 2004/02/29
Re: [avr-libc-dev] patch for iom162.h - signal name consistency, E. Weddington, 2004/02/26