compiler parser bug

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

Fabian.

why? why should REM blocks work different from any other BitzMax Block?

I know that it looks a bit inconsistently that rem differs from the other enclosing commands in BMX, however, comments should be treated differently since the characters they enclose are in contrast to the other block statements not compiled but are completely ignored. Therefore you can't interleave them:

Rem
Rem
EndRem
EndRem

doesn't work, so it makes no sense to expect from Rem/EndRem to work exactly the same like the others (While/EndWhile, Select/EndSelect....). So it wouldn't hurt any principles of BMX to let this behaviour as it is currently.

Why isn't it compiling this code!? Oh ... the previously included file had an open REM block. There's an hour of my life down the drain

Try this:

file1.bmx:

Strict
Framework brl.blitz

Include "file2.bmx"

WriteStdout "This gets printed, and that's the correct behaviour!~n"

file2.bmx:

Rem

All comment blocks are closed at eof (singleline as well as multiline)