1
1
Fork 0
mirror of https://github.com/QB64Official/qb64.git synced 2024-07-20 18:35:15 +00:00
qb64/internal/help/$CHECKING.txt
Luke Ceddia b586eafd3b Integrated _BLINEINPUT into regular LINE INPUT for BINARY files
LINE INPUT will now use the faster method if passed a file handle
that has been opened FOR BINARY. As such, the _BLINEINPUT command
has been removed.

qb64.bas now takes advantage of this for reading from '$include files,
at least in Include Manager 1. Some tweaking of internal/source/main.txt
was required to get things into a sane state, so I'm holing off changing
the compiler any further so the auto-builder can make sure everything's
smoothed over.

Note: Everything should still compile as normal; I'm just being overcautious.
2014-07-27 00:06:17 +10:00

31 lines
1.1 KiB
Plaintext

The $CHECKING metacommand turns C++ event checking ON or OFF.
''Syntax:'' $CHECKING:OFF
* The Metacommand does '''NOT''' require a comment or REM before it! There is no space after the colon.
* The OFF action turns event checking off and should '''ONLY be used when running stable, errorless code!'''
* The default $CHECKING:ON action is only required when checking has been turned OFF previously.
* When $CHECKING:OFF is used, all error code and the reporting code is removed from the EXE program.
* '''WARNING! Turning OFF error checking could create a General Protection Fault!'''
''Explanation:'' After every QB64 command a C++ check as follows is performed: If (qbevent){...
: Using [[ON TIMER (n)]] merely sets qbevent when appropriate, causing little/no difference to the speed your program runs. Unless you are using the QB64 direct meta-command to avoid this:
:::$CHECKING:OFF
:But turning checking off is only designed for 100% stable, error-less sections of code, where every CPU cycle saved counts. Such as in a software 3D texture mapper.
''See also:''
* [[ON TIMER(n)]]
* [[ON ERROR]]
* [[Metacommand]]
* [[ERROR Codes]]
{{PageNavigation}}