Darn it! My blasted syntax highlighter is always confused by that dratted var:)
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
| [reply] |
Maybe it suggests that you should not use the var ;-)
The syntax highlighter built into SciTE gets confused from time to time as well ... but generaly I think I improve the code if I change it to suite SciTE. If the code confused the parser it might as well confuse a programmer. Especialy if he uses something that highlights it wrong.
Jenda
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
Edit by castaway: Closed small tag in signature
| [reply] |
On this occasion, it wasn't my theoretical code that theoretically threw my syntax highlighter into a spin. Theoretically:) And I'm not going to be the one to risk Abigail-II's wroth by suggesting that $" should never be used!
In reality, the only time $" ever appears in my code, it is always localised, always on a line on its own, and always followed by a comment eg.
local $" = ', '; #"
The " in the comment serving to pair the first for the syntax highlighter.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
| [reply]
[d/l] |