Error 024 break or continue is out of context

• Errors
001 — expected token: token, but found token
A required token is omitted.
002 — only a single statement (or expression) can follow each “case”
Every case in a switch statement can hold exactly one statement. To put multiple statements in a case, enclose these statements between braces (which creates a compound statement).
003 — declaration of a local variable must appear in a compound block
The declaration of a local variable must appear between braces (“{. . .}”) at the active scope level.
When the parser flags this error, a variable declaration appears as the only statement of a function or the only statement below an if, else, for, while or do statement. Note that, since local variables are accessible only from (or below) the scope that their declaration appears in, having a variable declaration as the only statement at any scope is useless.
004 — function name is not implemented
There is no implementation for the designated function. The function may have been “forwardly” declared —or prototyped— but the full function definition including a statement, or statement block, is missing.
005 — function may not have arguments
The function main is the program entry point. It may not have arguments.
006 — must be assigned to an array
String literals or arrays must be assigned to an array. This error message may also indicate a missing index (or indices) at the array on the right side of the “=” sign.
007 — operator cannot be redefined
Only a select set of operators may be redefined, this operator is not one of them. See page 84 for details.
008 — must be a constant expression; assumed zero
The size of arrays and the parameters of most directives must be constant values.
009 — invalid array size (negative, zero or out of bounds)
The number of elements of an array must always be 1 or more. In addition, an array that big that it does exceeds the range of a cell is invalid too.
010 — illegal function or declaration
The compiler expects a declaration of a global variable or of a function at the current location, but it cannot interpret it as such.
011 — invalid outside functions
The instruction or statement is invalid at a global level. Local labels and (compound) statements are only valid if used within functions.
012 — invalid function call, not a valid address
The symbol is not a function.
013 — no entry point (no public functions)
The file does not contain a main function or any public function. The compiled file thereby does not have a starting point for the execution.
014 — invalid statement; not in switch
The statements case and default are only valid inside a switch statement.
015 — “default” must be the last clause in switch statement pawn requires the default clause to be the last clause in a switch statement.
016 — multiple defaults in “switch”
Each switch statement may only have one default clause.
017 — undefined symbol symbol
The symbol (variable, constant or function) is not declared.
018 initialization data exceeds declared size
Initialization: 63
An array with an explicit size is initialized, but the number of initiallers exceeds the number of elements specified. For example, in “arr[3]={1,2,3,4};” the array is specified to have three elements, but there are four initiallers.
019 — not a label: name
A goto statement branches to a symbol that is not a label.
020 — invalid symbol name
A symbol may start with a letter, an underscore or an “at” sign (“@”) and may be followed by a series of letters, digits, underscore characters and “@” characters.
021 — symbol already defined: identifier
The symbol was already defined at the current level.
022 — must be lvalue (non-constant)
The symbol that is altered (incremented, decremented, assigned a value, etc.) must be a variable that can be modified (this kind of variable is called an lvalue). Functions, string literals, arrays and constants are no lvalues. Variables declared with the “const” attribute are no lvalues either.
023 — array assignment must be simple assignment
When assigning one array to another, you cannot combine an arithmetic operation with the assignment (e.g., you cannot use the “+=” operator).
024 — “break” or “continue” is out of context
The statements break and continue are only valid inside the context of a loop (a do, for or while statement). Unlike the languages C/C++ and Java, break does not jump out of a switch statement.
025 — function heading differs from prototype
The number of arguments given at a previous declaration of the function does not match the number of arguments given at the current declaration.
026 — no matching “#if…”
The directive #else or #endif was encountered, but no matching #if directive was found.
027 — invalid character constant
One likely cause for this error is the occurrence of an unknown escape sequence, like “x”. Putting multiple characters between single quotes, as in ’abc’ also issues this error message. A third cause for this error is a situation where a character constant was expected, but none (or a non-character expression) were provided.
028 — invalid subscript (not an array or too many subscripts): identifier
The subscript operators “[” and “]” are only valid with arrays. The number of square bracket pairs may not exceed the number of dimensions of the array.
029 — invalid expression, assumed zero
The compiler could not interpret the expression.
030 — compound statement not closed at the end of file (started at line number)
An unexpected end of file occurred. One or more compound statements are still unfinished (i.e. the closing brace “}” has not been found). The line number where the compound statement started is given in the message.
031 — unknown directive
The character “#” appears first at a line, but no valid directive was specified.
032 — array index out of bounds
The array index is larger than the highest valid entry of the array.
033 — array must be indexed (variable name)
An array as a whole cannot be used in a expression; you must indicate an element of the array between square brackets.
034 — argument does not have a default value (argument index)
You can only use the argument placeholder when the function definition specifies a default value for the argument.
035 — argument type mismatch (argument index)
The argument that you pass is different from the argument that the function expects, and the compiler cannot convert the passed-in argument to the required type. For example, you cannot pass the literal value “1” as an argument when the function expects an array or a reference.
036 — empty statement
The line contains a semicolon that is not preceded by an expression. pawn does not support a semicolon as an empty statement, use an empty compound block instead.
037 — invalid string (possibly non-terminated string)
A string was not well-formed; for example, the final quote that ends a string is missing, or the filename for the #include directive was not enclosed in double quotes or angle brackets.
038 — extra characters on line
There were trailing characters on a line that contained a directive (a directive starts with a # symbol, see page 116).
039 — constant symbol has no size
A variable has a size (measured in a number of cells), a constant has no size. That is, you cannot use a (symbolic) constant with the sizeof operator, for example.
040 — duplicate “case” label (value value)
A preceding “case label” in the list of the switch statement evaluates to the same value.
041 — invalid ellipsis, array size is not known
You used a syntax like “arr[] = { 1, … };”, which is invalid, because the compiler cannot deduce the size of the array from the declaration.
042 — invalid combination of class specifiers
A function or variable is denoted as both “public” and “native”, which is unsupported. Other combinations may also be unsup- ported; for example, a function cannot be both “public” and “stock” (a variable may be declared both “public” and “stock”).
043 — character constant value exceeds range for a packed string/array
When the error occurs on a literal string, it is usually an attempt to store a Unicode character in a packed string where a packed character is 8-bits. For a literal array, one of the constants does not fit in the range for packed characters.
044 — positional parameters must precede all named parameters
When you mix positional parameters and named parameters in a function call, the positional parameters must come first.
045 — too many function arguments
The maximum number of function arguments is currently limited to 64.
046 — unknown array size (variable name)
For array assignment, the size of both arrays must be explicitly defined, also if they are passed as function arguments.
047 — array sizes do not match, or destination array is too small
For array assignment, the arrays on the left and the right side of the assignment operator must have the same number of dimensions. In addition:
— for multi-dimensional arrays, both arrays must have the same size —note that an unpacked array does not fit in a packed array with the same number of elements;
— for single arrays with a single dimension, the array on the left side of the assignment operator must have a size that is equal or bigger than the one on the right side.
When passing arrays to a function argument, these rules also hold for the array that is passed to the function (in the function call) versus the array declared in the function definition.
When a function returns an array, all return statements must specify an array with the same size and dimensions.
048 — array dimensions do not match
For an array assignment, the dimensions of the arrays on both sides of the “=” sign must match; when passing arrays to a function argument, the arrays passed to the function (in the function call) must match with the definition of the function arguments.
When a function returns an array, all return statements must specify an array with the same size and dimensions.
049 — invalid line continuation
A line continuation character (a backslash at the end of a line) is at an invalid position, for example at the end of a file or in a single line comment.
050 — invalid range
A numeric range with the syntax “n1 .. n2”, where n1 and n2 are numeric constants, is invalid. Either one of the values in not a valid number, or n1 is not smaller than n2.
051 — invalid subscript, use “[ ]” operators on major dimensions and for named indices
You can use the “character array index” operator (braces: “{ }” only for the last dimension, and only when indexing the array with a number. For other dimensions, and when indexing the array with a “symbolic index” (one that starts with a “.”), you must use the cell index operator (square brackets: “[ ]”).
052 — multi-dimensional arrays must be fully initialized
If an array with more than one dimension is initialized at its declaration, then there must be equally many literal vectors/sub- arrays at the right of the equal sign (“=”) as specified for the major dimension(s) of the array.
053 — exceeding maximum number of dimensions
The current implementation of the pawn compiler only supports arrays with one or two dimensions.
054 — unmatched closing brace
A closing brace (“}”) was found without matching opening brace (“{”).
055 — start of function body without function header
An opening brace (“{”) was found outside the scope of a function. This may be caused by a semicolon at the end of a preceding function header.
056 — arrays, local variables and function arguments cannot be public
A local variable or a function argument starts with the character “@”, which is invalid.
057 — unfinished expression before compiler directive
Compiler directives may only occur between statements, not inside a statement. This error typically occurs when an expression statement is split over multiple lines and a compiler directive appears between the start and the end of the expression. This is not supported.
058 — duplicate argument; same argument is passed twice
In the function call, the same argument appears twice, possibly through a mixture of named and positional parameters.
059 — function argument may not have a default value (variable name)
All arguments of public functions must be passed explicitly. Public functions are typically called from the host application, who has no knowledge of the default parameter values. Arguments of user defined operators are implied from the expression and cannot be inferred from the default value of an argument.
060 — multiple “#else” directives between “#if . . . #endif
Two or more #else directives appear in the body between the matching #if and #endif.
061 — “#elseif” directive follows an “#else” directive
All #elseif directives must appear before the #else directive. This error may also indicate that an #endif directive for a higher level is missing.
062 — number of operands does not fit the operator
When redefining an operator, the number of operands that the operator has (1 for unary operators and 2 for binary operators) must be equal to the number of arguments of the operator function.
063 — function result tag of operator name must be name
Logical and relational operators are defined as having a result that is either true (1) or false (0) and having a “bool:” tag. A user defined operator should adhere to this definition.
064 — cannot change predefined operators
One cannot define operators to work on untagged values, for example, because pawn already defines this operation.
065 — function argument may only have a single tag (argument number)
In a user defined operator, a function argument may not have multiple tags.
066 — function argument may not be a reference argument or an array (argument number)
In a user defined operator, all arguments must be cells (non-arrays) that are passed “by value”.
067 — variable cannot be both a reference and an array (variable name)
A function argument may be denoted as a “reference” or as an array, but not as both.
068 — invalid rational number precision in #pragma
The precision was negative or too high. For floating point rational numbers, the precision specification should be omitted.
069 — rational number format already defined
This #pragma conflicts with an earlier #pragma that specified a different format.
070 — rational number support was not enabled
A rational literal number was encountered, but the format for rational numbers was not specified.
071 — user-defined operator must be declared before use (func- tion name)
Like a variable, a user-defined operator must be declared before its first use. This message indicates that prior to the declaration of the user-defined operator, an instance where the operator was used on operands with the same tags occurred. This may either indicate that the program tries to make mixed use of the default operator and a user-defined operator (which is unsupported), or that the user-defined operator must be “forwardly declared”.
072 — “sizeof” operator is invalid on “function” symbols
You used something like “sizeof MyCounter” where the symbol “MyCounter” is not a variable, but a function. You cannot request the size of a function.
073 — function argument must be an array (argument name)
The function argument is a constant or a simple variable, but the function requires that you pass an array.
074 — #define pattern must start with an alphabetic character
Any pattern for the #define directive must start with a letter, an underscore (“_”) or an “@”-character. The pattern is the first word that follows the #define keyword.
075 — input line too long (after substitutions)
Either the source file contains a very long line, or text substitutions make a line that was initially of acceptable length grow beyond its bounds. This may be caused by a text substitution that causes recursive substitution (the pattern matching a portion of the replacement text, so that this part of the replacement text is also matched and replaced, and so forth).
076 — syntax error in the expression, or invalid function call
The expression statement was not recognized as a valid statement (so it is a “syntax error”). From the part of the string that was parsed, it looks as if the source line contains a function call in a “procedure call” syntax (omitting the parentheses), but the function result is used —assigned to a variable, passed as a parameter, used in an expression. . .
077 — malformed UTF-8 encoding, or corrupted file: filename
The file starts with an UTF-8 signature, but it contains encodings that are invalid UTF-8. If the source file was created by an editor or converter that supports UTF-8, the UTF-8 support is non-conforming.
078 — function uses both “return” and “return <value>”
The function returns both with and without a return value. The function should be consistent in always returning with a function result, or in never returning a function result.
079 — inconsistent return types (array & non-array)
The function returns both values and arrays, which is not allowed. If a function returns an array, all return statements must specify an array (of the same size and dimensions).
080 — unknown symbol, or not a constant symbol (symbol name)
Where a constant value was expected, an unknown symbol or a non-constant symbol (variable) was found.
082 — user-defined operators and native functions may not have states
Only standard and public functions may have states.
083 — a function or variable may only belong to a single automa- ton (symbol name)
There are multiple automatons in the state declaration for the indicated function or variable, which is not supported. In the case of a function: all instances of the function must belong to the same automaton. In the case of a variable: it is allowed to have several variables with the same name belonging to different automatons, but only in separate declarations —these are distinct variables.
084 — state conflict: one of the states is already assigned to another implementation (symbol name)
The specified state appears in the state specifier of two implemen- tations of the same function.
085 — no states are defined for symbol name
When this error occurs on a function, this function has a fall-back implementation, but no other states. If the error refers to a variable, this variable does not have a list of states between the < and > characters. Use a state-less function or variable instead.
086 — unknown automaton name
The “state” statement refers to an unknown automaton.
087 — unknown state name for automaton name
The “state” statement refers to an unknown state (for the specified automaton).
088 — public variables and local variables may not have states (symbol name)
Only standard (global) variables may have a list of states (and an automaton) at the end of a declaration.
089 — state variables may not be initialized (symbol name)
Variables with a state list may not have initializers. State variables should always be initialized through an assignment (instead of at their declaration), because their initial value is indeterminate.
090 — public functions may not return arrays (symbol name)
A public function may not return an array. Returning arrays is allowed only for normal functions.
091 — first constant in an enumerated list must be initialized (symbol name)
The first constant in a list of enumerated symbolic constants must be set to a value. Any subsequent symbol is automatically set the the value of the preceding symbol +1.
092 — invalid number format
A symbol started with a digit, but is is not a valid number.
093 — array fields with a size may only appear in the final dimension
In the final dimension (the “minor” dimension), the fields of an array may optionally be declared with a size that is different from a single cell. On the major dimensions of an array, this is not valid, however.
094 — invalid subscript, subscript does not match array definition regarding named indices (symbol name)
Either the array was declared with symbolic subscripts and you are indexing it with an expression, or you are indexing the array with a symbolic subscript which is not defined for the array.
• Fatal Errors
100 — cannot read from file: filename
The compiler cannot find the specified file or does not have access to it.
101 — cannot write to file: filename
The compiler cannot write to the specified output file, probably caused by insufficient disk space or restricted access rights (the file could be read-only, for example).
102 — table overflow: table name
An internal table in the pawn parser is too small to hold the required data. Some tables are dynamically growable, which means that there was insufficient memory to resize the table. The “table name” is one of the following:
“staging buffer”: the staging buffer holds the code generated for an expression before it is passed to the peephole optimizer. The
staging buffer grows dynamically, so an overflow of the staging buffer basically is an “out of memory” error.
“loop table”: the loop table is a stack used with nested do, for, and while statements. The table allows nesting of these statements up to 24 levels.
“literal table”: this table keeps the literal constants (numbers, strings) that are used in expressions and as initiallers for arrays. The literal table grows dynamically, so an overflow of the literal table basically is an “out of memory” error.
“compiler stack”: the compiler uses a stack to store temporary information it needs while parsing. An overflow of this stack is probably caused by deeply nested (or recursive) file inclusion. The compiler stack grows dynamically, so an overflow of the compiler stack basically is an “out of memory” error.
“option table”: in case that there are more options on the command line or in the response file than the compiler can cope with.
103 — insufficient memory
General “out of memory” error.
104 — incompatible options: option versus option
Two option that are passed to the pawn compiler conflict with each other, or an option conflicts with the configuration of the pawn compiler.
105 — numeric overflow, exceeding capacity
A numeric constant, notably a dimension of an array, is too large for the compiler to handle. For example, when compiled as a 16-bit application, the compiler cannot handle arrays with more than 32767 elements.
106 — compiled script exceeds the maximum memory size
(number bytes)
The memory size for the abstract machine that is needed to run the script exceeds the value set with #pragma amxlimit. This means that the script is too large to be supported by the host.
You might try reducing the script’s memory requirements by:
— setting a smaller stack/heap area —see #pragma dynamic at page 119;
— using packed strings instead of unpacked strings —see pages 99 and 136;
— using overlays —see pages 120 and page 170 for more information on overlays.
— putting repeated code in separate functions;
— putting repeated data (strings) in global variables;
— trying to find more compact algorithms to perform the same task.
107 — too many error/warning messages on one line
A single line that causes several error/warning messages is often an indication that the pawn parser is unable to “recover” from an earlier error. In this situation, the parser is unlikely to make any sense of the source code that follows —producing only (more) inappropriate error messages. Therefore, compilation is halted.
108 — codepage mapping file not found
The file for the codepage translation that was specified with the -c compiler option or the #pragma codepage directive could not be loaded.
109 — invalid path: path name
A path, for example for include files or codepage files, is invalid. Check the compiler options and, if used, the configuration file.
110 — assertion failed: expression
Compile-time assertion failed.
111 — user error: message
The parser fell on an #error directive.
112 — overlay function name exceeds limit by value bytes
The size of a function is too large for the overlay system. To fix this issue, you will have to split the function into two (or more) functions.
• Warnings
200 — symbol is truncated to number characters
The symbol is longer than the maximum symbol length. The maximum length of a symbol depends on whether the symbol is native, public or neither. Truncation may cause different symbol names to become equal, which may cause error 021 or warning 219.
201 — redefinition of constant/macro (symbol name)
The symbol was previously defined to a different value, or the text substitution macro that starts with the prefix name was redefined with a different substitution text.
202 — number of arguments does not match definition
At a function call, the number of arguments passed to the function (actual arguments) differs from the number of formal arguments declared in the function heading. To declare functions with variable argument lists, use an ellipsis (…) behind the last known argument in the function heading; for example: print(formatstring,…); (see page 78).
203 — symbol is never used: identifier
A symbol is defined but never used. Public functions are excluded from the symbol usage check (since these may be called from the outside).
204 — symbol is assigned a value that is never used: identifier
A value is assigned to a symbol, but the contents of the symbol are never accessed.
205 — redundant code: constant expression is zero
Where a conditional expression was expected, a constant expression with the value zero was found, e.g. “while (0)” or “if (0)”. The the conditional code below the test is never executed, and it is therefore redundant.
206 — redundant test: constant expression is non-zero
Where a conditional expression was expected, a constant expression with a non-zero value was found, e.g. if (1). The test is redundant, because the conditional code is always executed.
To create an endless loop, use for ( ;; ) instead of while (1).
207 — unknown “#pragma”
The compiler ignores the pragma. The #pragma directives may change between compilers of different vendors and between different versions of a compiler of the same version.
208 — function with tag result used before definition, forcing
reparse
When a function is “used” (invoked) before being declared, and that function returns a value with a tag name, the parser must make an extra pass over the source code, because the presence of the tag name may change the interpretation of operators (in the presence of user-defined operators). You can speed up the parsing/compilation process by declaring the relevant functions before using them.
209 — function should return a value
The function does not have a return statement, or it does not have an expression behind the return statement, but the function’s result is used in a expression.
210 — possible use of symbol before initialization: identifier
A local (uninitialized) variable appears to be read before a value is assigned to it. The compiler cannot determine the actual order of reading from and storing into variables and bases its assumption of the execution order on the physical appearance order of statements an expressions in the source file.
211 — possibly unintended assignment
Where a conditional expression was expected, the assignment operator (=) was found instead of the equality operator (==). As this is a frequent mistake, the compiler issues a warning. To avoid this message, put parentheses around the expression, e.g. if ( (a=2) ).
212 — possibly unintended bitwise operation
Where a conditional expression was expected, a bitwise operator (& or |) was found instead of a Boolean operator (&& or ||). In situations where a bitwise operation seems unlikely, the compiler issues this warning. To avoid this message, put parentheses around the expression.
213 — tag mismatch
A tag mismatch occurs when:
— assigning to a tagged variable a value that is untagged or that has a different tag
— the expressions on either side of a binary operator have different tags
— in a function call, passing an argument that is untagged or that has a different tag than what the function argument was defined with
— indexing an array which requires a tagged index with no tag or a wrong tag name
214 — possibly a “const” array argument was intended: identifier
Arrays are always passed by reference. If a function does not modify the array argument, however, the compiler can sometimes generate more compact and quicker code if the array argument is specifically marked as “const”.
215 — expression has no effect
The result of the expression is apparently not stored in a variable or used in a test. The expression or expression statement is therefore redundant.
216 — nested comment
pawn does not support nested comments.
217 — loose indentation
Statements at the same logical level do not start in the same column; that is, the indents of the statements are different. Although pawn is a free format language, loose indentation frequently hides a logical error in the control flow.
The compiler can also incorrectly assume loose indentation if the tab size with which you indented the source code differs from the assumed size. This may happen if the source files use a mixture of tab and space characters to indent lines. Sometimes it is then needed to tell the pawn parser what tab size to use, see #pragma tabsize on page 121 or the compiler option -t on page 170.
You can also disable this warning with #pragma tabsize 0 or the compiler option -t:0.
218 — old style prototypes used with optional semicolon
When using “optional semicolons”, it is preferred to explicitly declare forward functions with the forward keyword than using terminating semicolon.
219 — local variable identifier shadows a symbol at a preceding level
A local variable has the same name as a global variable, a function, a function argument, or a local variable at a lower precedence level. This is called “shadowing”, as the new local variable makes the previously defined function or variable inaccessible.
Note: if there are also error messages further on in the script about missing variables (with these same names) or brace level problems, it could well be that the shadowing warnings are due to these syntactical and semantical errors. Fix the errors first before looking at the shadowing warnings.
220 — expression with tag override must appear between paren- theses
In a case statement and in expressions in the conditional operator (“ ? : ”), any expression that has a tag override should be en- closed between parentheses, to avoid the colon to be misinterpreted as a separator of the case statement or as part of the conditional operator.
221 — label name identifier shadows tag name
A code label (for the goto instruction) has the same name as a previously defined tag. This may indicate a faultily applied tag override; a typical case is an attempt to apply a tag override on the variable on the left of the = operator in an assignment statement.
222 — number of digits exceeds rational number precision
A literal rational number has more decimals in its fractional part than the precision of a rational number supports. The remaining decimals are ignored.
223 — redundant “sizeof”: argument size is always 1 (symbol name)
A function argument has a as its default value the size of another argument of the same function. The “sizeof” default value is only useful when the size of the referred argument is unspecified in
the declaration of the function; i.e., if the referred argument is an array.
224 — indeterminate array size in “sizeof” expression (symbol name)
The operand of the sizeof operator is an array with an unspecified size. That is, the size of the variable cannot be determined
at compile time. If used in an “if” instruction, consider a conditionally compiled section, replacing if by #if.
225 — unreachable code
The indicated code will never run, because an instruction before (above) it causes a jump out of the function, out of a loop or elsewhere. Look for return, break, continue and goto instructions above the indicated line. Unreachable code can also be caused by an endless loop above the indicated line.
226 — a variable is assigned to itself (symbol name)
There is a statement like “x = x” in the code. The parser checks for self assignments after performing any text and constant substitutions, so the left and right sides of an assignment may appear to be different at first sight. For example, if the symbol “TWO” is a constant with the value 2, then “var[TWO] = var[2]” is also a self-assignment.
Self-assignments are, of course, redundant, and they may hide an error (assignment to the wrong variable, error in declaring constants).
Note that the pawn parser is limited to performing “static checks” only. In this case it means that it can only compare array assignments for self-assignment with constant array indices.
227 — more initiallers than array fields
An array that is declared with sumbolic subscripts contains more values/fields as initiallers than there are (symbolic) subscripts.
228 — length of initialler exceeds size of the array field
The initialler for an array element contains more values than the size of that field allows. This occurs in an array that has symbolic subscripts, and where a particular subscript is declared with a size.
229 — mixing packed and unpacked array indexing or array assignment
An array is declared as packed (with { and } braces) but indexed as unpacked (with [ and ]), or vice versa. Or one array is assigned to another and one is packed while the other is unpacked.
230 — no implementation for state name in function name, no fall-back
A function is lacking an implementation for the indicated state. The compiler cannot (statically) check whether the function will ever be called in that state, and therefore it issues this warning. When the function would be called for the state for which no implementation exists, the abstract machine aborts with a run time error.
See page 81 on how to specify a fall-back function, and page 42 for a description and an example.
231 — state specification on forward declaration is ignored
A state specification is redundant on forward declarations. The function signature must be equal for all states. Only the imple- mentations of the function are state-specific.
232 — native function lacks a predefined index (symbol name)
The pawn compiler was configured with predefined indices for native functions, but it encountered a declaration for which it does not have an index declaration. This usually means that the script uses include files that arenot appropriate for the active configuration.
233 — state variable name shadows a global variable
The state variable has the same name as a global variable (without state specifiers). This means that the global variable is inaccessible for a function with one of the same states as those of the variable.
234 — function is deprecated (symbol name)
The script uses a function which as marked as “deprecated”. The host application can mark (native) functions as deprecated when better alternatives for the function are available or if the function may not be supported in future versions of the host application.
235 — public function lacks forward declaration (symbol name)
The script defines a public function, but no forward declaration of this function is present. Possibly the function name was written incorrectly. The requirement for forward declarations of public functions guards against a common error.
236 — unknown parameter in substitution (incorrect #define pattern)
A #define pattern contains a parameter in the replacement (e.g. “%1”), that is not in the match pattern. See page 92 for the preprocessor syntax.
237 — recursive function name
The specified function calls itself recursively. Although this is valid in pawn, a self-call is often an error. Note that this warning is only generated when the pawn parser/compiler is set to “verbose” mode.
238 — mixing string formats in concatenation
In concatenating literals strings, strings with different formats (such as packed versus unpacked, and “plain” versus standard strings) were combined. This is usually an error. The parser uses the format of the first (left-most) string in the concatenation for the result.

Source — here you can also view notices which are described above.

Содержание

1. Errors List
2. From SA-MP Wiki
3. Contents
4. General Pawn Error List
5. Error categories
6. Errors
7. Fatal errors
8. Warnings
9. Common Errors
10. 001: expected token
11. 002: only a single statement (or expression) can follow each “case”
12. 004: function «x» is not implemented
13. 025: function heading differs from prototype
14. 035: argument type mismatch (argument x)
15. 036: empty statement
16. 046: unknown array size (variable x)
17. 047: array sizes do not match, or destination array is too small
18. 055: start of function body without function header
19. Common Fatal Errors
20. 100: cannot read from file: » «
21. Common Warnings
22. 202: number of arguments does not match definition
23. 203: symbol is never used: «symbol»
24. 204: symbol is assigned a value that is never used: «symbol»
25. 209: function should return a value
26. 211: possibly unintended assignment
27. 213: tag mismatch
28. 217: loose indentation
29. 219: local variable «foo» shadows a variable at a preceding level
30. 225: unreachable code
31. 235: public function lacks forward declaration (symbol «symbol»)
32. Error 001 expected token but found return
33. Вопросы
34. Error 001 expected token but found return
35. Поделиться сообщением
36. 7 ответов на этот вопрос
37. Последние посетители 0 пользователей онлайн
38. Похожий контент
39. Исправляем ошибки/предупреждения
40. Batka1337
41. Форум Pawn.Wiki — Воплоти мечту в реальность!: error 001: expected token: «;», but found «return» — Форум Pawn.Wiki — Воплоти мечту в реальность!