> All that said, it is extraordinarily *bad* design to exploit 
> case-sensitivity in displays of nerdismo such as defining distinct 
> commands or identifiers that differ only in case.

If I ever find the time for a Jal-version-2 I'll make it
case-insensitive but case-enforcing: the use of an identifier must match
the definition exactly (including case), and defining another identifier
that differs only in case is not allowed.

> (There's also an admonition in there that the names of 
> symbolic constants need to reflect the *purpose* of the 
> constant rather than its *value*; 

That's my argument againts
- that weird notation where the type of a variable reflects its
structure
- USING ALL UPPERCASE FOR C DEFINES

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

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