[avr-gcc-list] Re: More interrupt oddity

[Mike Dombrowski]

On 21 Oct 2001, at 12:01, address@hidden wrote:

> Ok, I solved my own problem. What I did wrong was this:
> 
> 
> volatile char displacement;
> 
> SIGNAL(SIG_INTERUPT0) <------notice mis-spelling, should be
> SIG_INTERRUPT0
> {                                   with 2 R's
>  --displacement;
> }
> 
> The goofy part is that the linker didn't give any errors or warnings
> that something may be wrong. Shouldn't it fail with an undefined
> symbol or something?

I believe the interrupt routines are defined as macros, so running 
the macro with a bad input would just not meet and #IF and thus 
nothing would be put in your code as a result of the macro. I may 
be wrong tho, the way to check is to look at the header.

Mike