>> the normal C convention of using uppercase for all macro's is bad, =20
>> it takes the readers attention away from the few cases that need =20
>> attention.

I dunno; identifying the macro as a macro is only one purpose of using =20
uppercase.
The other is to prevent collisions with other namespaces.  Having =20
something like:

#define iobit 0x40

void writebit(unsigned char iobit, unsigned char value)
{
  ...
}

can result in rather confusing error messages from the compiler.

BillW

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.