QB64may need a complete rewrite to address this hoffific bug I found!

[Pete]

Code: QB64: [Select]

1. $IF  THEN
2.     Value = 0: (Valid)   Array is empty with no EOL.
3.     Value = 1: (Invalid) Array is empty but has a EOL added. This should not be present, but I think it occurs when a line is initially erased. This needs more investigation.
4.     Value > 1: (Valid)   Array contains text.
5. $END IF
6.  
7. $IF  THEN
8.     Value = 0: [Valid]   Array is empty with no EOL.
9.     Value = 1: {Invalid} Array is empty but has a EOL added. This should not be present, but I think it occurs when a line is initially erased. This needs more investigation.
10.     Value > 1: |Valid|   Array contains text.
11. $END IF
12.  

So a trick to write block REM statements. It works great, unless you throw in brackets or some other characters, which are rejected by the IDE. In the code above, the first BLOCK REM is accepted, but the {{ and | characters will all bomb out in the second example.

So let me know when the complete rewrite is finished. :D

Actually, I do get what these metacommands were meant for, a way to conditionally include or exclude program code in the final compilation, but it would be nice to have a $REM $END REM someday.

Pete

Go Dodgers!

[SMcNeill]

Honestly, I'm surprised that QB64 tosses those errors for us.  We should kick out of the reading/processing those lines completely, if the $IF block is invalid.  Since I haven't ran across this glitch in the past, I've never had to sort out where the syntax check for invalid characters pops up in the processing order of things.  I'd imagine the fix to this is probably just as simple as cutting/pasting the $IF process before the syntax checking process.  I'll dig into it later, when I get a little free time, if nobody else hunts down what needs to change operation order for us first.;)