BL> Incredible! Paul follows a standard which surrounds every
 BL> sinple if() {}; with the curly brackets over four lines, even
 BL> when it is asingle statement best placed on one line to be read
 BL> at once. This means that a string of simple if(){}; becomes
 BL> almost incomprehensible inside a larger loop or whatever!

 PE> Funny, you were just complaining about short-hand. Basically,
 PE> if your loop is so large that it can't handle that, it's too
 PE> large anyway, time to split off into a function. 

  I was talking about readability; a single if(); statement... not a
multifunction statement and the indented curly brackets that are the 
bane of C readability.

 BL> Borland solved it with the one-line comment "//" but this isn't
 BL> ANSI

 PE> That's C++, not Borland. It's part of the C++ standard.

  Perhaps you could explain the error in my original statement. Is it
ANSI, or not? And did Borland solve it with "//" or not?

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---