| FlashBASIC Differences | Index Level | format strings |
| Syntax | |
| Category | BASIC |
| Type | Definition |
| Description |
describes how to record compiling errors when using FlashBASIC.
When compiling ("flashing") Pick/BASIC programs with the "o" option, the compiler automatically logs all compilation errors, if there is a data section called "$log" present in the user's Pick/BASIC program file. The log is updated ONLY when errors occur. Each log entry's id is the same as the id of the item being compiled. The first attribute of the entry consists of the time and date that the error occurred as well as the "phase" of compilation where the error occured. Other attributes may contain additional undefined information which may contain Unix error messages. Errors logged as "phase 0" errors are problems detected by the standard Pick/BASIC compiler. Errors logged as "phase 1" and higher are FlashBASIC compilation errors. Errors occuring higher can indicate an installation problem or lack of some resource, such as swap space. In these cases, attributes 2 and higher contain more exact error reporting. |
| Options | |
| See Also | compile basic FlashBASIC FlashBASIC Differences FlashBASIC performance $log |
| Example |
To enable logging for a file called "bp", type the following:
create-file bp,$log 7 From then on, all compile's which use the "o" option will log errors into the "bp,$log" file and may be displayed by typing: ct bp,$log or list-item bp,$log or sort-item bp,$log |
| Warnings | |
| Compatibility | AP 6.0 FlashBASIC |
| FlashBASIC Differences | Index Level | format strings |