previous next top contents index framed top this page unframed
| Temporary feature: subject to change |
Figure 47–28. $setSystemBit
| <macro> $setSystemBit (BITS b); |
$setSystemBit sets various bits, called system bits, that control MAINSAIL execution. The possible arguments and their meanings are:
| System Bit | Meaning |
|---|---|
| $swapBit | Write swapping information to TTY as if the MAINEX SWAPINFO subcommand had been given. |
| $memInfoBit | Write memory management information to TTY as if the MAINEX MEMINFO subcommand had been given. |
| $mapAtMemInfoBit | Write memory maps as if the MAINEX MAP subcommand (with no arguments) had been given. |
| $noCheckConsistency | Do not perform interface consistency checking when MODULEs are bound, as if the MAINEX NOCHECKCONSISTENCY subcommand had been given. |
| $fileInfoBit | Write file information to TTY as if the FILEINFO subcommand had been given. |
| $controlInfoBit | Write coroutine and exception information to TTY as if the CONTROLINFO subcommand had been given. |
| noResponse | Responses are not requested from errMsg as if the NORESPONSE MAINEX or compiler subcommand had been given. |
Only the above bits should be changed. Changing other system bits from a program has undefined effects. Users must reference bits by identifier only, not by value, since their values may change in future releases. Some bits may become obsolete. Some configuration bits (see the description of $setConfigurationBit) may become system bits or vice versa. The type(s) of the configuration and/or system bits are subject to change; e.g., they may become LONG BITS.
$clrSystemBit is used to clear bits set with $setSystemBit.
MAINSAIL Language Manual, Section 47.24