Difference between revisions of "Custom Compiler Modes"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | == OpenQM GPL Compatibility Compiler Modes == | + | == ScarletDME/OpenQM GPL Compatibility Compiler Modes == |
===HEADING.NO.EJECT=== | ===HEADING.NO.EJECT=== | ||
| Line 12: | Line 12: | ||
---- | ---- | ||
| − | == OpenQM GPL Custom Compiler Modes == | + | == ScarletDME/OpenQM GPL Custom Compiler Modes == |
===NO.CASE.INVERT=== | ===NO.CASE.INVERT=== | ||
This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified. | This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified. | ||
Latest revision as of 15:03, 25 June 2013
Contents
ScarletDME/OpenQM GPL Compatibility Compiler Modes
HEADING.NO.EJECT
This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.
NO.ECHO.DATA
This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.
ScarletDME/OpenQM GPL Custom Compiler Modes
NO.CASE.INVERT
This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.
