Collective memory

Abigail abigail at abigail.nl
Fri Jul 11 07:08:44 EDT 2003


Walter Bushell (proto at panix.com) wrote on MMMDC September MCMXCIII in
<URL:news:1fxw51u.2b4m6zc39wulN%proto at panix.com>:
++  Charles Richmond <richmond at ev1.net> wrote:
++ <Snip>
++ > int  *p, x, y;
++ > 
++ > then:
++ > 
++ >     y = x/*p;
++ > 
++ > is quite different from:
++ > 
++ >     y = x / *p;
++ > 
++ > The first way, "/*" will begin a comment...the second way,
++ > you get the integer "x" divided by the integer pointed to by "p".
++  
++  Ouch!! That is one reason code coloring is *important*.

Nope. That's a reason why code colouring is evil. If you write code,
and it isn't clear what you mean without the use of code colouring,
you did something wrong. Your code shouldn't rely on a specific code
colouring scheme to be understandable.

All in my opinion of course.


Abigail




More information about the Python-list mailing list