Revision history for ProPgComments


Revision [21203]

Last edited on 2016-03-13 12:30:46 by fxm [Formatting]
Additions:







Revision [20628]

Edited on 2016-02-10 16:12:33 by DkLwikki [Update link format]
Additions:
A source code statement beginning with ##[[KeyPgRem|Rem]]## indicates that the line is comment and will not be compiled. In ""FreeBASIC"", ##[[KeyPgRem|Rem]]## may also appear after other keywords on a source line and the behavior is the same as above (only the rest of the statement will be treated as a comment).
Metacommands, such as ##[[KeyPgMetaStatic|$static]]## and ##[[KeyPgMetaInclude|$include]]##, can be placed in single-line comments. The ##**$**## sign and the keyword must be the first two things in the statement, not including white space.
~&//Note: As of version 0.21.0, this will not longer apply in the //[[CompilerOptlang|-lang fb]]// dialect, and multi-line comment markers will be completely ignored inside single-line comments//
- ##[[KeyPgRem|Rem]]##
Deletions:
A source code statement beginning with ##[[KeyPgRem Rem]]## indicates that the line is comment and will not be compiled. In ""FreeBASIC"", ##[[KeyPgRem Rem]]## may also appear after other keywords on a source line and the behavior is the same as above (only the rest of the statement will be treated as a comment).
Metacommands, such as ##[[KeyPgMetaStatic $static]]## and ##[[KeyPgMetaInclude $include]]##, can be placed in single-line comments. The ##**$**## sign and the keyword must be the first two things in the statement, not including white space.
~&//Note: As of version 0.21.0, this will not longer apply in the //[[CompilerOptlang -lang fb]]// dialect, and multi-line comment markers will be completely ignored inside single-line comments//
- ##[[KeyPgRem Rem]]##


Revision [19837]

Edited on 2016-01-22 08:02:00 by FxMwikki [In FB, REM may also appear after other keywords on a source line]
Additions:
A source code statement beginning with ##[[KeyPgRem Rem]]## indicates that the line is comment and will not be compiled. In ""FreeBASIC"", ##[[KeyPgRem Rem]]## may also appear after other keywords on a source line and the behavior is the same as above (only the rest of the statement will be treated as a comment).
Deletions:
A source code statement beginning with ##[[KeyPgRem Rem]]## indicates that the rest of the line is comment and will not be compiled. ##[[KeyPgRem Rem]]## behavior is the same as above, except it must be the first keyword in the statement.


Revision [14143]

Edited on 2009-05-25 20:49:29 by CountingPine [In lang fb, m-line comments will not be allowed anywhere in s-line comments in the next release]
Additions:
Note: If ""FreeBASIC"" encounters a close-comment marker while it's not in a multi-line comment, it will treat it as a normal single-line comment due to the single quote.
A multi-line comment can contain unlimited levels of nested comments. ""FreeBASIC"" will continue to parse the multi-line comment for more markers until the number of close-comment markers reaches the number of open-comment markers, i.e. when it has closed all the comments it has opened.
A single-line comment may appear after the line continuation character ( ##**_**## ) in a multi-line statement. ""FreeBASIC"" does not parse the text after the line continuation character, though, so you can't open multi-line comments after them.
When you make a single-line comment, ""FreeBASIC"" will parse the comment, to check for a metacommand. If it finds a multi-line comment, it will treat it as usual, and continue parsing the single-line comment after the close-comment marker.
If you want to prevent ""FreeBASIC"" parsing the single-line comment, put another single quote (##**'**##), at the start of the comment. ""FreeBASIC"" will treat the rest of the line, including multi-line comment markers and metacommands, as ordinary text, and will ignore it. Other words encountered in a comment will also stop the parsing.
~&//Note: As of version 0.21.0, this will not longer apply in the //[[CompilerOptlang -lang fb]]// dialect, and multi-line comment markers will be completely ignored inside single-line comments//
Deletions:
Note: If FreeBASIC encounters a close-comment marker while it's not in a multi-line comment, it will treat it as a normal single-line comment due to the single quote.
A multi-line comment can contain unlimited levels of nested comments. FreeBASIC will continue to parse the multi-line comment for more markers until the number of close-comment markers reaches the number of open-comment markers, i.e. when it has closed all the comments it has opened.
A single-line comment may appear after the line continuation character ( ##**_**## ) in a multi-line statement. FreeBASIC does not parse the text after the line continuation character, though, so you can't open multi-line comments after them.
When you make a single-line comment, FreeBASIC will parse the comment, to check for a metacommand. If it finds a multi-line comment, it will treat it as usual, and continue parsing the single-line comment after the close-comment marker.
If you want to prevent FreeBASIC parsing the single-line comment, put another single quote (##**'**##), at the start of the comment. FreeBASIC will treat the rest of the line, including multi-line comment markers and metacommands, as ordinary text, and will ignore it. Other words encountered in a comment will also stop the parsing.


Revision [13546]

Edited on 2008-07-21 15:43:00 by JeffMarshall [added #lang or $lang to example]
Additions:
Rem compile With -lang fblite Or qb
#lang "fblite"
Deletions:
Rem compile with -lang fblite or qb


Revision [12774]

The oldest known version of this page was created on 2008-04-01 15:44:53 by JeffMarshall [added #lang or $lang to example]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki



sf.net phatcode