


95 Illegal inside a compound statement or scoped block.86 Var-len strings cannot be initialized.85 -pic used, but not supported by target system (only works for non-x86 Unixes).84 -pic used when making executable (only works when making a shared library).83 -asm att used for -gen gas, but -gen gas only supports -asm intel.82 Selected -gen gas ASM backend for non-x86 CPU.81 Selected non-x86 CPU when compiling for DOS.76 '.' ellipsis upper bound given for array field (this is not supported).75 '.' ellipsis upper bound given for dynamic array (this is not supported).74 Var-len arrays cannot be initialized.61 Statement in between SELECT and first CASE.54 Fixed-len strings cannot be returned from functions.52 Illegal outside a CONSTRUCTOR, DESTRUCTOR, FUNCTION, OPERATOR, PROPERTY or SUB block.43 Illegal outside a compound statement.39 Expected 'END SUB' or 'END FUNCTION'.38 'SUB' or 'FUNCTION' without 'END SUB' or 'END FUNCTION'.37 Array boundaries do not match the original EXTERN declaration.

In a few cases the place pointed at by the error messages is not where the errors can be found, it's the place where the compiler has given up in waiting for something that should be somewhere. The compiler signals the lines where the errors have been found, so the correction can be done quickly. The error messages stop the compilation after 10 errors (see the -maxerr command-line option to change that default value) or a fatal error occurred, and require a correction by the user before the compilation can be continued. 38 Mixing operand data types may have undefined results.34 '=' parsed as equality operator in function argument, not assignment to BYREF function result.33 Shift value greater than or equal to number of bits in data type.32 'IF' statement found directly after multi-line 'ELSE'.30 Command line option overrides directive.26 Variable following NEXT is meaningless.24 Variable too large for stack, consider making it SHARED.23 Array too large for stack, consider making it var-len or SHARED.21 Object files or libraries with mixed language (-lang) options.20 Object files or libraries with mixed multithreading (-mt) options.19 The ANY initializer has no effect on UDT's with default constructors.18 The length of the parameters list is too large, consider passing UDT's BYREF.17 The type length is too large, consider passing BYREF.14 Branch crossing local variable definition.13 Function result was not explicitly set.12 Missing closing quote in literal string.10 UDT with pointer or var-len string fields.6 Cannot export symbol without -export option.Sometimes one of these operations is coded deliberately to achieve a result, in this case the warnings can be disabled by setting the -w 1 option at the command line. The warnings don't stop the compilation, just alert the user some non-recommended and error-prone operation is attempted in the code.
