I'm sorry, but the benefits that you get from applying unicode translations that early in the game are not nearly enough to justify side-effects like this.
Parse out comments first, then handle things like escapes, unicode translations, and the like.
This also means that // Some text \
Really shouldn't result in the comment continuing on in the next line.
I kind of get their argument, but I'm seriously opposed to the result existing. :)
But this kind of thing makes reading the code that much more difficult, and it makes it significantly easier to write things that look like they are doing one thing when they are actually doing another.
That is bad enough as an accident, and is really bad when it is intentional.
I may be biased by my work environment, but at least 50% of the job of any program is to be fully readable at 3am after an hour of sleep. If the code works but doesn't pass that test, it's just as broken as code that works but which you can't understand.
When you're faced with regulatory environments that require you to actually review code and say that it does what it says it does, you have a different set of 'even the less experienced programmers need to be able to read this reliably' requirements.
I'm having a lot of trouble finding any benefit to the compiler parsing unicode before comments, but I'm finding plenty of ways to abuse it.
5
u/ShadowPouncer May 11 '18
... No, just, no.
I'm sorry, but the benefits that you get from applying unicode translations that early in the game are not nearly enough to justify side-effects like this.
Parse out comments first, then handle things like escapes, unicode translations, and the like.
This also means that // Some text \
Really shouldn't result in the comment continuing on in the next line.
I kind of get their argument, but I'm seriously opposed to the result existing. :)