> But then it should be accompanied with extra documentation 
> explaining what's going on.

Of course. Nobody said the code shown wasn't.

> All too often I see people writing code like that 
> just because
> they can and because they think it's cool to use the standard 
> constructs in
> novel ways, and it's a plus that others have to "figure out" 
> what the code
> does.

That is a sure reason to demote (or promote?) a programmer to a position
where he is not allowed to come near to a computer. Probably to a
management position, with an obligation to grow pointy hair :(

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