Re: [avr-gcc-list] Feature request - compiler warning for "if" stmts that do nothing

[E. Weddington]

Bob Paddock wrote:

> > the time when you accidently put = instead of ==, but some times it's what
> >    
>
> If you want to save yourself debugging time get in the habit of putting
> the constants on the left:
>
> while (0 == (SPSR & (1 << SPIF))
> ;
>
> while ((SPSR & (1 << SPIF)) = 0)
> ;
> would be an error that some compilers say nothing about.
>
> The compiler will always barf if the constant is on the left because
> you can not assign a value to a constant.
>
>  

GCC will give you a warning if the constant is on the right, and you 
accidentally use an assignment in an if statement. Try it and see.

Eric