Difference between revisions of "Zbex comments"
Jump to navigation
Jump to search
(added chapter navigator at bottom of page) |
(added chapter navigator at top of page) |
||
| Line 1: | Line 1: | ||
| + | {{ZbexChap | ||
| + | | before = [[Zbex input and output|Input and output]] | ||
| + | | after = [[Zbex subscripts|Subscripts]] | ||
| + | }} | ||
| + | |||
| + | |||
You can include comments in your Zbex code. In Zbex, each statement occupies exactly one line. The compiler scans the line from left to right. If it encounters the character pattern <tt>/*</tt>, it treats everything that follows as a comment. | You can include comments in your Zbex code. In Zbex, each statement occupies exactly one line. The compiler scans the line from left to right. If it encounters the character pattern <tt>/*</tt>, it treats everything that follows as a comment. | ||
Revision as of 06:12, 15 October 2010
| Previous chapter Input and output |
Zbex Manual |
Next Chapter Subscripts |
You can include comments in your Zbex code. In Zbex, each statement occupies exactly one line. The compiler scans the line from left to right. If it encounters the character pattern /*, it treats everything that follows as a comment.
If a line has a star (*) in column one, or if column one is highlighted with a color, the entire line is treated as a comment.
The color-comment feature, latter feature makes it easy to comment out (change code lines to comment lines) whole sections of code. You simply use the box highlight to highlight column one of all the lines you wish to comment out and then press F6 to turn that column red.
| Previous chapter Input and output |
Zbex Manual |
Next Chapter Subscripts |