DAY 011: REM

[mnrvovrfc]

As is, folks have two ways of coding data with remarks wrong, but they won't be stung until runtime. Since runtime yields a syntax error, the user is going to be scratching his head wondering why the IDE let the syntax error compile.

Pete

It's like the glitch you discovered the other day! The user has to have some common sense while using the product. No developers want to slave over minute details of getting this little bit just right, even if they're being paid for it. Just put the comment in a separate line from any valid code line. Relying on the colon only to place a comment on the same line as code is the sign of sloppy programming. I would reject that if it's not for a "this number of lines" programming contest and even if there are more valid English clauses in it than stuff to be parsed. Tell the kids not to be lazy like C++ programmers that screamed out for that double-slash and made sure many other languages had it also.

Remarks being colored because the IDE thinks they are valid statements: don't sweat any of that stuff. If this is too confusing then use another text editor to create source code.

Be glad QB64PE is not like Lua. How to deal with this many equals signs when plain double-bracket isn't good enough to start a comment or delimit a string full of single- and double-quotation marks...

I was going to request code-folding in the IDE, and '{ and '} supported for the user to enforce it on a block. Imagine that.