Flags

///FLAGS:[flag] [flag] ... - Since R3

Flags have been temporarily removed from R5 Beta (Not compiled)

The flags command will technically work but it won't change the output in any way, R5 has been all about rewriting basic features and i could not get around doing command line flags.

---

This is a special command, it only works if it is in the FIRST line of a file.bpp
It allows you to define flags for that program ignoring the command line ones
(This command is not mandatory, in case this line is not found, the compiler will use the console args)
Putting this command anywhere else in the file, will result in it getting removed.

WARNING! IF YOU ARE USING R3, PLEASE DO NOT USE THIS!
R3 HAD A BUG WHERE THE CODE WOULD COUNT THE FLAG LINE BUT NOT DISPLAY IT, MAKING GOTOs JUMP TO THE WRONG LINES

Example:

Source

///FLAGS:-r -kc

///,teststring="This is just a test for flags"
rem this comment should stay
print ///teststring///
rem and here there should be a run

Compiled

10 rem this comment should stay
20 print "This is just a test for flags"
30 rem and here there should be a run
run

More on: Flags

for optimization purposes, by default, the ///. will not be replaced by a rem, BUT this makes stuff like this:

///.a
///;10
print "a"
goto a

return an error because line 10 does not exist.

you can, of course, change this!
just run the compiler with the -ur flag!
C64Compiler.exe/.py file.bpp [-ur or --userem] - Since R1
if you wish to automatically put in a newline instead of the :, then use the flag -rmc
C64Compiler.exe/.py file.bpp [-rmc or --removecolon] - Since R1 (not recommended)
if you wish to keep comments in your code, use the flag -kc
C64Compiler.exe/.py file.bpp [-kc or --keepcomments] - Since R1
if you wish to add the run at the end of your code, use the flag -r
C64Compiler.exe/.py file.bpp [-r or --run] - Since R2
if you dont want the compiler to halt at the end, use the flag -ne
C64Compiler.exe/.py file.bpp [-ne or --noerrors] - Since R2