paweld/fpc
1
0
Fork 0
mirror of https://gitlab.com/freepascal.org/fpc/source.git synced 2025-08-18 18:49:27 +02:00
Code Issues Packages Projects Releases Wiki Activity

* new messages file generated.

Browse Source
This commit is contained in:
michael 1999-04-10 14:45:57 +00:00
parent 9881d340cc
commit d83d1ac357
1 changed files with 261 additions and 135 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

234
docs/messages.tex
View File

@ -1,10 +1,11 @@
\section{General compiler messages} \section{General compiler messages}
This section gives the compiler messages which are not fatal, but which This section gives the compiler messages which are not fatal, but which
display useful information. The number of such messages can be display useful information. The number of such messages can be
controlled with the various verbosity level \var{-v} switches. controlled with the various verbosity level \var{-v} switches.
\begin{description} \begin{description}
\item [Compiler: arg1] \item [Compiler: arg1]
When the \var{-vu} switch is used, this line tells you what compiler When the \var{-vt} switch is used, this line tells you what compiler
is used. is used.
\item [Source OS: arg1] \item [Source OS: arg1]
When the \var{-vd} switch is used, this line tells you what the source When the \var{-vd} switch is used, this line tells you what the source
@ -13,21 +14,21 @@
When the \var{-vd} switch is used, this line tells you what the target When the \var{-vd} switch is used, this line tells you what the target
operating system is. operating system is.
\item [Using executable path: arg1] \item [Using executable path: arg1]
When the \var{-vu} switch is used, this line tells you where the compiler When the \var{-vt} switch is used, this line tells you where the compiler
looks for it's binaries. looks for it's binaries.
\item [Using unit path: arg1] \item [Using unit path: arg1]
When the \var{-vu} switch is used, this line tells you where the compiler When the \var{-vt} switch is used, this line tells you where the compiler
looks for compiled units. You can set this path with the \var{-Fu} or looks for compiled units. You can set this path with the \var{-Fu} or
\var{-Up} options. \var{-Up} options.
\item [Using include path: arg1] \item [Using include path: arg1]
When the \var{-vu} switch is used, this line tells you where the compiler When the \var{-vt} switch is used, this line tells you where the compiler
looks for it's include files (files used in \var{\{\$I xxx\}} statements). looks for it's include files (files used in \var{\{\$I xxx\}} statements).
You can set this path with the \var{-I} option. You can set this path with the \var{-I} option.
\item [Using library path: arg1] \item [Using library path: arg1]
When the \var{-vu} switch is used, this line tells you where the compiler When the \var{-vt} switch is used, this line tells you where the compiler
looks for the libraries. You can set this path with the \var{-Fl} option. looks for the libraries. You can set this path with the \var{-Fl} option.
\item [Using object path: arg1] \item [Using object path: arg1]
When the \var{-vu} switch is used, this line tells you where the compiler When the \var{-vt} switch is used, this line tells you where the compiler
looks for object files you link in (files used in \var{\{\$L xxx\}} statements). looks for object files you link in (files used in \var{\{\$L xxx\}} statements).
You can set this path with the \var{-Fo} option. You can set this path with the \var{-Fo} option.
\item [Info: arg1 Lines compiled, arg2 sec] \item [Info: arg1 Lines compiled, arg2 sec]
@ -66,12 +67,12 @@
multiple lines. multiple lines.
\item [Fatal: illegal character] \item [Fatal: illegal character]
An illegal character was encountered in the input file. An illegal character was encountered in the input file.
\item [Fatal: Syntax error arg1 expected] \item [Fatal: Syntax error arg1 expected but arg2 found]
This indicates that the compiler expected a different token than This indicates that the compiler expected a different token than
the one you typed. It can occur almost everywhere where you make a the one you typed. It can occur almost everywhere where you make a
mistake against the pascal language. mistake against the pascal language.
\item [Start reading includefile arg1] \item [Start reading includefile arg1]
When you provide the \var{-vu} switch, the compiler tells you When you provide the \var{-vt} switch, the compiler tells you
when it starts reading an included file. when it starts reading an included file.
\item [Warning: Comment level arg1 found] \item [Warning: Comment level arg1 found]
When the \var{-vw} switch is used, then the compiler warns you if When the \var{-vw} switch is used, then the compiler warns you if
@ -119,7 +120,7 @@
\item [Warning: Macro contents is cut after char 255 to evalute expression] \item [Warning: Macro contents is cut after char 255 to evalute expression]
The contents of macros canno be longer than 255 characters. This is a The contents of macros canno be longer than 255 characters. This is a
safety in the compiler, to prevent buffer overflows. This is shown as a safety in the compiler, to prevent buffer overflows. This is shown as a
wraning, i.e. when the \var{-vw} switch is used. warning, i.e. when the \var{-vw} switch is used.
\item [Error: ENDIF without IF(N)DEF] \item [Error: ENDIF without IF(N)DEF]
Your \var{\{\$IFDEF ..\}} and {\{\$ENDIF\}} statements aren't balanced. Your \var{\{\$IFDEF ..\}} and {\{\$ENDIF\}} statements aren't balanced.
\item [Fatal: User defined: arg1] \item [Fatal: User defined: arg1]
@ -181,11 +182,26 @@
When warings are turned on (\var{-vw}) the compiler warns you about When warings are turned on (\var{-vw}) the compiler warns you about
unrecognised switches. For a list of recognised switches, \progref unrecognised switches. For a list of recognised switches, \progref
\item [Back in arg1] \item [Back in arg1]
When debugging messages are on (\var{-vd}) the compiler tells you when When you use (\var{-vt}) the compiler tells you when it has finished
it has finished reading an include file. reading an include file.
\item [Warning: Unsupported application type: arg1]
You get this warning, ff you specify an unknown application type
with the directive \{\$APPTYPE\}
\item [Warning: argAPPTYPE isn't support by the target OS]
The \{\$APPTYPE\} directive is supported by win32 applications only
\item [Warning: Unsupported assembler style specified arg1] \item [Warning: Unsupported assembler style specified arg1]
When you specify an assembler mode with the \var{\{\$ASMMODE xxx\}} When you specify an assembler mode with the \var{\{\$ASMMODE xxx\}}
the compiler didn't recognize the mode you specified. the compiler didn't recognize the mode you specified.
\item [Warning: ASM reader switch is not possible inside asm statement arg1 will be effective only for next]
It is not possible to switch from one assembler reader to another
inside an assmebler block. The new reader will be used for next
assembler statement only.
\item [Error: Wrong switch toggle, use ON/OFF or +/-]
You need to use ON or OFF or a + or - to toggle the switch
\item [Error: Resource files are not supported for this target]
The target you are compiling for doesn't support Resource files. The
only target which can use resource files is Win32
\end{description} \end{description}
\section{Parser messages} \section{Parser messages}
This section lists all parser messages. The parser takes care of the This section lists all parser messages. The parser takes care of the
@ -201,8 +217,17 @@
\item [Warning: Procedure type NEAR ignored] \item [Warning: Procedure type NEAR ignored]
This is a warning. \var{NEAR} is a construct for 8 or 16 bit programs. Since This is a warning. \var{NEAR} is a construct for 8 or 16 bit programs. Since
the compile generates 32 bit programs, it ignores this directive. the compile generates 32 bit programs, it ignores this directive.
\item [Warning: Procedure type REGISTER ignored]
This is a warning. \var{REGISTER} is ignored by FPC programs for now.
This is introduced first for Delphi compatibility.
\item [Error: No DLL File specified] \item [Error: No DLL File specified]
No longer in use. No longer in use.
\item [Error: DLL exported function names cannot be double arg1]
Exported function names inside a specific DLL must all be different
\item [Error: DLL exported function indexes cannot be double arg1]
Exported function names inside a specific DLL must all be different
\item [Error: Invalid index for DLL exported function]
DLL function index must be in the range 1..\$FFFF
\item [Error: Constructor name must be INIT] \item [Error: Constructor name must be INIT]
You are declaring a constructor with a name which isn't \var{init}, and the You are declaring a constructor with a name which isn't \var{init}, and the
\var{-Ss} switch is in effect. See the \var{-Ss} switch (\seeo{Ss}). \var{-Ss} switch is in effect. See the \var{-Ss} switch (\seeo{Ss}).
@ -228,7 +253,7 @@
\item [Error: Local class definitions are not allowed] \item [Error: Local class definitions are not allowed]
Classes must be defined globally. They cannot be defined inside a Classes must be defined globally. They cannot be defined inside a
procedure or function procedure or function
\item [Error: Anonym class definitions are not allowed] \item [Fatal: Anonym class definitions are not allowed]
An invalid object (class) declaration was encountered, i.e. an An invalid object (class) declaration was encountered, i.e. an
object or class without methods that isn't derived from another object or object or class without methods that isn't derived from another object or
class. For example: class. For example:
@ -238,16 +263,17 @@
end; end;
\end{verbatim} \end{verbatim}
will trigger this error. will trigger this error.
\item [Error: The object arg1 has no VMT]
\item [Error: Illegal parameter list] \item [Error: Illegal parameter list]
You are calling a function with parameters that are of a different type than You are calling a function with parameters that are of a different type than
the declared parameters of the function. the declared parameters of the function.
\item [Error: Wrong parameter type specified] \item [Error: Wrong parameter type specified for arg NN]
There is an error in the parameter list of the function or procedure. There is an error in the parameter list of the function or procedure.
The compiler cannot determine the error more accurate than this. The compiler cannot determine the error more accurate than this.
\item [Error: Wrong amount of parameters specified] \item [Error: Wrong amount of parameters specified]
There is an error in the parameter list of the function or procedure, There is an error in the parameter list of the function or procedure,
the number of parameters is not correct. the number of parameters is not correct.
\item [Error: overloaded identifier isn't a function identifier] \item [Error: overloaded identifier arg1 isn't a function]
The compiler encountered a symbol with the same name as an overloaded The compiler encountered a symbol with the same name as an overloaded
function, but it isn't a function it can overload. function, but it isn't a function it can overload.
\item [Error: overloaded functions have the same parameter list] \item [Error: overloaded functions have the same parameter list]
@ -255,27 +281,38 @@
Overloaded function must have at least 1 different parameter in their Overloaded function must have at least 1 different parameter in their
declaration. declaration.
\item [Error: function header doesn't match the forward declaration arg1] \item [Error: function header doesn't match the forward declaration arg1]
You declared a function with same parameters but
different result type or function specifiers.
\item [Error: function header arg1 doesn't match forward : var name changes arg2 => arg3]
You declared the function in the \var{interface} part, or with the You declared the function in the \var{interface} part, or with the
\var{forward} directive, but define it with a different parameter list. \var{forward} directive, but define it with a different parameter list.
\item [Note: only values can be jumped over in enumeration types] \item [Note: only values can be jumped over in enumeration types]
\fpc allows enumeration constructions as in C. Given the following \fpc allows enumeration constructions as in C. Given the following
declaration two declarations: declaration two declarations:
\begin{verbatim} \begin{verbatim}
type a = (A_A,A_B,A_E=:6,A_UAS:=200); type a = (A_A,A_B,A_E:=6,A_UAS:=200);
type a = (A_A,A_B,A_E=:6,A_UAS:=4); type a = (A_A,A_B,A_E:=6,A_UAS:=4);
\end{verbatim} \end{verbatim}
The second declaration would produce an error. \var{A\_UAS} needs to have a The second declaration would produce an error. \var{A\_UAS} needs to have a
value higher than \var{A\_E}, i.e. at least 7. value higher than \var{A\_E}, i.e. at least 7.
\item [Note: Interface and implementation names are different !] \item [Note: Interface and implementation names are different !]
This note warns you if the implementation and interface names of a This note warns you if the implementation and interface names of a
functions are different, but they have the same mangled name. This functions are different, but they have the same mangled name. This
is important when using overloaded functions. is important when using overloaded functions (but should produce no error).
\item [Error: With can not be used for variables in a different segment]
With stores a variable locally on the stack,
but this is not possible if the variable belongs to another segment.
\item [Error: function nesting > 31] \item [Error: function nesting > 31]
You can nest function definitions only 31 times. You can nest function definitions only 31 times.
\item [Error: range check error while evaluating constants] \item [Error: range check error while evaluating constants]
The constants are out of their allowed range. The constants are out of their allowed range.
\item [Warning: range check error while evaluating constants]
The constants are out of their allowed range.
\item [Error: duplicate case label] \item [Error: duplicate case label]
You are specifying the same label 2 times in a \var{case} statement. You are specifying the same label 2 times in a \var{case} statement.
\item [Error: Upper bound of case range is less than lower bound]
The upper bound of a \var{case} label is less than the lower bound and this
is useless
\item [Error: typed constants of classes are not allowed] \item [Error: typed constants of classes are not allowed]
You cannot declare a constant of type class or object. You cannot declare a constant of type class or object.
\item [Error: functions variables of overloaded functions are not allowed] \item [Error: functions variables of overloaded functions are not allowed]
@ -283,7 +320,7 @@
This isn't allowed. This isn't allowed.
\item [Error: string length must be a value from 1 to 255] \item [Error: string length must be a value from 1 to 255]
The length of a string in Pascal is limited to 255 characters. You are The length of a string in Pascal is limited to 255 characters. You are
trying to declare a string with length greater than 255. trying to declare a string with length lower than 1 or greater than 255
(This is not true for \var{Longstrings} and \var{AnsiStrings}. (This is not true for \var{Longstrings} and \var{AnsiStrings}.
\item [Warning: use extended syntax of DISPOSE and NEW to generate instances of objects] \item [Warning: use extended syntax of DISPOSE and NEW to generate instances of objects]
If you have a pointer \var{a} to a class type, then the statement If you have a pointer \var{a} to a class type, then the statement
@ -296,6 +333,8 @@
a dot, a dot,
i.e., a object or class method, but the type in front of the dot is not i.e., a object or class method, but the type in front of the dot is not
a known type. a known type.
\item [Error: type identifier not allowed here]
You cannot use a type inside an expression.
\item [Error: method identifier expected] \item [Error: method identifier expected]
This identifier is not a method. This identifier is not a method.
This happens when the compiler scans a procedure declaration that contains This happens when the compiler scans a procedure declaration that contains
@ -356,6 +395,8 @@
exist. exist.
\item [Error: No member is provided to access property] \item [Error: No member is provided to access property]
You specified no \var{read} directive for a property. You specified no \var{read} directive for a property.
\item [Warning: Stored prorperty directive is not yet implemented]
The \var{stored} directive is not yet implemented
\item [Error: Illegal symbol for property access] \item [Error: Illegal symbol for property access]
There is an error in the \var{read} or \var{write} directives for an array There is an error in the \var{read} or \var{write} directives for an array
property. When you declare an array property, you can only access it with property. When you declare an array property, you can only access it with
@ -374,9 +415,12 @@
Fields that are declared in a \var{private} section of an object or class Fields that are declared in a \var{private} section of an object or class
declaration cannot be accessed outside the module where the class is declaration cannot be accessed outside the module where the class is
defined. defined.
\item [Warning: overloaded of virtual method must be virtual: arg1] \item [Warning: overloaded method of virtual method should be virtual: arg1]
If you declare overloaded methods in a class, then they should either all be If you declare overloaded methods in a class, then they should either all be
virtual, or none. You cannot mix them. virtual, or none. You shouldn't mix them.
\item [Warning: overloaded method of non-virtual method should be non-virtual: arg1]
If you declare overloaded methods in a class, then they should either all be
virtual, or none. You shouldn't mix them.
\item [Error: overloaded methods which are virtual must have the same return type: arg1] \item [Error: overloaded methods which are virtual must have the same return type: arg1]
If you declare virtual overloaded methods in a class definition, they must If you declare virtual overloaded methods in a class definition, they must
have the same return type. have the same return type.
@ -604,6 +648,30 @@
Properties in a \var{published} section cannot be array properties. Properties in a \var{published} section cannot be array properties.
they must be moved to public sections. Properties in a \var{published} they must be moved to public sections. Properties in a \var{published}
section must be an ordinal type, a real type, strings or sets. section must be an ordinal type, a real type, strings or sets.
\item [Warning: Empty import name specified]
Both index and name for the import are 0 or empty
\item [Warning: Empty import name specified]
Some targets need a name for the imported procedure or a cdecl specifier
\item [Error: Function internal name changed after use of function]
\item [Error: Division by zero]
There is a divsion by zero encounted
\item [Error: Invalid floating point operation]
An operation on two real type values produced an overflow or a division
by zero.
\item [Error: Upper bound of range is less than lower bound]
The upper bound of a \var{case} label is less than the lower bound and this
is not possible
\item [Error: string length is larger than array of char length]
The size of the constant string is larger than the size you specified in
the array[x..y] of char definition
\item [Error: Illegal expression after message directive]
\fpc supports only integer or string values as message constants
\item [Error: Message handlers can take only one call by ref. parameter]
A method declared with the \var{message}-directive as message handler
can take only one parameter which must be declared as call by reference
Parameters are declared as call by reference using the \var{var}-directive
\item [Error: Duplicate message label: arg1]
A label for a message is used twice in one object/class
\end{description} \end{description}
\section{Type checking errors} \section{Type checking errors}
This section lists all errors that can occur when type checking is This section lists all errors that can occur when type checking is
@ -647,18 +715,19 @@
\item [Error: Can't evaluate constant expression] \item [Error: Can't evaluate constant expression]
No longer in use. No longer in use.
\item [Error: Set elements are not compatible] \item [Error: Set elements are not compatible]
You are trying to take the union of two set, when the set element types You are trying to make an operation on two sets, when the set element types
are not the same. The base type of a set must be the same when taking the are not the same. The base type of a set must be the same when taking the
union union
\item [Error: Operation not implemented for sets]
several binary operations are not defined for sets
like div mod ** (also >= <= for now)
\item [Warning: Automatic type conversion from floating type to COMP which is an integer type] \item [Warning: Automatic type conversion from floating type to COMP which is an integer type]
An implicit type conversion from a real type to a \var{comp} is An implicit type conversion from a real type to a \var{comp} is
encountered. Since \var{Comp} is a 64 bit integer type, this may indicate encountered. Since \var{Comp} is a 64 bit integer type, this may indicate
an error. an error.
\item [Warning: Using / will give a floating point result]
When using the '/' operator in \fpc the result will be of type real, when
used with integers.
\item [Hint: use DIV instead to get an integer result] \item [Hint: use DIV instead to get an integer result]
When hints are on, then an integer division will procuce this message. When hints are on, then an integer division with the '/' operator will
procuce this message, because the result will then be of type real
\item [Error: string types doesn't match, because of argV+ mode] \item [Error: string types doesn't match, because of argV+ mode]
When compiling in \var{\{\$V+ \}} mode, the string you pass as a parameter When compiling in \var{\{\$V+ \}} mode, the string you pass as a parameter
should be of the exact same type as the declared parameter of the procedure. should be of the exact same type as the declared parameter of the procedure.
@ -676,8 +745,15 @@
\item [Error: Type conflict between set elements] \item [Error: Type conflict between set elements]
There is at least one set element which is of the wrong type, i.e. not of There is at least one set element which is of the wrong type, i.e. not of
the set type. the set type.
\item [Warning: lo/hi(longint/dword) returns the upper/lower word]
\fpc supports an overloaded version of \var{lo/hi} for \var{longint/dword}
which returns the lower/upper word of the argument. TP always uses
a 16 bit \var{lo/hi} which returns always bits 0..7 for \var{lo} and the
bits 8..15 for \var{hi}. If you want the TP behavior you have
to type case the argument to \var{word/integer}
\item [Error: Integer or real expression expected] \item [Error: Integer or real expression expected]
The first argument to \var{str} must a real or integer type. The first argument to \var{str} must a real or integer type.
\item [Error: Wrong type in array constructor]
\end{description} \end{description}
\section{Symbol handling} \section{Symbol handling}
This section lists all the messages that concern the handling of symbols. This section lists all the messages that concern the handling of symbols.
@ -696,7 +772,7 @@
\item [Error: Unknown identifier arg1] \item [Error: Unknown identifier arg1]
The identifier encountered hasn't been declared, or is used outside the The identifier encountered hasn't been declared, or is used outside the
scope where it's defined. scope where it's defined.
\item [Error: Forward declaration not solved: arg1] \item [Error: Forward declaration not solved arg1]
This can happen in two cases: This can happen in two cases:
\begin{itemize} \begin{itemize}
\item This happens when you declare a function (in the \var{interface} part, or \item This happens when you declare a function (in the \var{interface} part, or
@ -706,11 +782,13 @@
\end{itemize} \end{itemize}
\item [Fatal: Identifier type already defined as type] \item [Fatal: Identifier type already defined as type]
You are trying to redefine a type. You are trying to redefine a type.
\item [Error: Error in type defenition] \item [Error: Error in type definition]
There is an error in your definition of a new array type: There is an error in your definition of a new array type:
\item One of the range delimiters in an array declaration is erroneous. \item One of the range delimiters in an array declaration is erroneous.
For example, \var{Array [1..1.25]} will trigger this error. For example, \var{Array [1..1.25]} will trigger this error.
\item [Error: Type identifier not defined] \item [Error: Type identifier not defined]
The type identifier has not been defined yet.
\item [Error: Forward type not resolved arg1]
The compiler encountered an unknown type. The compiler encountered an unknown type.
\item [Error: Only static variables can be used in static methods or outside methods] \item [Error: Only static variables can be used in static methods or outside methods]
A static method of an object can only access static variables. A static method of an object can only access static variables.
@ -723,16 +801,15 @@
\item [Error: Instances of classes or objects with an abtsract method are not allowed] \item [Error: Instances of classes or objects with an abtsract method are not allowed]
You are trying to generate an instance of a class which has an abstract You are trying to generate an instance of a class which has an abstract
method that wasn't overridden. method that wasn't overridden.
\item [Error: Label not defined arg1] \item [Warning: Label not defined arg1]
A label was declared, but not defined. A label was declared, but not defined.
\item [Error: Illegal label declaration] \item [Error: Illegal label declaration]
\item [Error: GOTO und LABEL are not supported (use command line switch -Sg)] \item [Error: GOTO und LABEL are not supported (use command line switch -Sg)]
\item [Error: Label not found]
A \var{goto label} was encountered, but the label isn't declared.
\item [GOTO and LABEL are not supported (use command line switch -Sg)]
You must compile a program which has \var{label}s and \var{goto} statements You must compile a program which has \var{label}s and \var{goto} statements
with the \var{-Sg} switch. By default, \var{label} and \var{goto} aren't with the \var{-Sg} switch. By default, \var{label} and \var{goto} aren't
supported. supported.
\item [Error: Label not found]
A \var{goto label} was encountered, but the label isn't declared.
\item [Error: identifier isn't a label] \item [Error: identifier isn't a label]
The identifier specified after the \var{goto} isn't of type label. The identifier specified after the \var{goto} isn't of type label.
\item [Error: label already defined] \item [Error: label already defined]
@ -744,7 +821,7 @@
\item [Hint: Parameter not used arg1] \item [Hint: Parameter not used arg1]
This is a warning. The identifier was declared (locally or globally) but This is a warning. The identifier was declared (locally or globally) but
wasn't used (locally or globally). wasn't used (locally or globally).
\item [Warning: Local variable not used arg1] \item [Note: Local variable not used arg1]
You have declared, but not used a variable in a procedure or function You have declared, but not used a variable in a procedure or function
implementation. implementation.
\item [Error: Set type expected] \item [Error: Set type expected]
@ -754,7 +831,7 @@
You can get this warning if the compiler thinks that a function return You can get this warning if the compiler thinks that a function return
value is not set. This will not be displayed for assembler procedures, value is not set. This will not be displayed for assembler procedures,
or procedures that contain assembler blocks. or procedures that contain assembler blocks.
\item [Error: Unknown field identifier] \item [Error: Unknown record field identifier arg1]
The field doesn't exist in the record definition. The field doesn't exist in the record definition.
\item [Warning: Local variable arg1 does not seem to be initialized] \item [Warning: Local variable arg1 does not seem to be initialized]
This message is displayed if the compiler thinks that a variable will This message is displayed if the compiler thinks that a variable will
@ -883,45 +960,57 @@
A procedure with a procedural variable call cannot be inlined. A procedure with a procedural variable call cannot be inlined.
\item [Error: No code for inline procedure stored] \item [Error: No code for inline procedure stored]
The compiler couldn't store code for the inline procedure. The compiler couldn't store code for the inline procedure.
\item [Error: Element zero of an ansi/wide- or longstring can't be accessed, use (set)length instead]
You should use \var{setlength} to set the length of an ansi/wide/longstring
and \var{length} to get the length of such kinf of string
\item [Error: Include or exclude not implemented in this case]
\var{include} and \var{exclude} are only partially
implemented for \var{i386} processors
and not at all for \var{m68k} processors.
\item [Constructors or destructors can not be called inside with here]
\end{description} \end{description}
\section{Unit loading messages.} \section{Unit loading messages.}
This section lists all messages that can occur when the compiler is This section lists all messages that can occur when the compiler is
loading a unit from disk into memory. Many of these mesages are loading a unit from disk into memory. Many of these mesages are
informational messages. informational messages.
\begin{description} \begin{description}
\item [Unitsearch: arg1]
When you use the \var{-vt}, the compiler tells you where it tries to find
unit files.
\item [PPU Loading arg1] \item [PPU Loading arg1]
When the \var{-vu} switch is used, the compiler tells you what units it When the \var{-vt} switch is used, the compiler tells you
loads. what units it loads.
\item [PPU Name: arg1]
When you use the \var{-vu} flag, the unit name is shown.
\item [PPU Flags: arg1]
When you use the \var{-vu} flag, the unit flags are shown.
\item [PPU Crc: arg1]
When you use the \var{-vu} flag, the unit CRC check is shown.
\item [PPU Time: arg1] \item [PPU Time: arg1]
When you use the \var{-vd} flag, the unit time is shown. When you use the \var{-vu} flag, the unit time is shown.
\item [PPU File too short] \item [PPU File too short]
When you use the \var{-vd} flag, the unit time is shown. When you use the \var{-vu} flag, the unit time is shown.
\item [PPU Invalid Header (no PPU at the begin)] \item [PPU Invalid Header (no PPU at the begin)]
A unit file contains as the first three bytes the ascii codes of \var{PPU} A unit file contains as the first three bytes the ascii codes of \var{PPU}
\item [PPU Invalid Version arg1] \item [PPU Invalid Version arg1]
This unit file was compiled with a different version of the compiler, and This unit file was compiled with a different version of the compiler, and
cannot be read. cannot be read.
\item [PPU Flags: arg1] \item [PPU is compiled for an other processor]
When you use the \var{-vd} flag, the unit flags are shown. This unit file was compiled for a different processor type, and
\item [PPU Crc: arg1] cannot be read
When you use the \var{-vd} flag, the unit CRC check is shown. \item [PPU is compiled for an other target]
This unit file was compiled for a different processor type, and
cannot be read
\item [PPU Source: arg1] \item [PPU Source: arg1]
When you use the \var{-vt} flag, the unit CRC check is shown. When you use the \var{-vu} flag, the unit CRC check is shown.
\item [objectfile and assemblerfile are older than ppufile]
When you use the \var{-vd} flag, the compiler warns if the assembler of
object file of the unit are older than the unit file itself.
\item [objectfile is older than assemblerfile]
When you use the \var{-vd} flag, the compiler warns if the assembler
file of the unit is older than the object file of the unit.
\item [Unitsearch: arg1]
When you use the \var{-vt}, the compiler tells ou where it tries to find
unt files.
\item [Writing arg1] \item [Writing arg1]
When you specify the \var{-vu} switch, the compiler will tell you where it When you specify the \var{-vu} switch, the compiler will tell you where it
writes the unit file. writes the unit file.
\item [Fatal: Can't Write PPU-File] \item [Fatal: Can't Write PPU-File]
An err An err
\item [Fatal: reading PPU-File] \item [Fatal: reading PPU-File]
Unexpected end of file
\item [Fatal: unexpected end of PPU-File]
This means that the unit file was corrupted, and contains invalid This means that the unit file was corrupted, and contains invalid
information. Recompilation will be necessary. information. Recompilation will be necessary.
\item [Fatal: Invalid PPU-File entry: arg1] \item [Fatal: Invalid PPU-File entry: arg1]
@ -935,7 +1024,7 @@
\fpc has a limit of 1024 units in a program. You can change this behavior \fpc has a limit of 1024 units in a program. You can change this behavior
by changing the \var{maxunits} constant in the \file{files.pas} file of the by changing the \var{maxunits} constant in the \file{files.pas} file of the
compiler, and recompiling the compiler. compiler, and recompiling the compiler.
\item [Fatal: Circular unit reference] \item [Fatal: Circular unit reference between arg1 and arg2]
Two units are using each other in the interface part. This is only allowed Two units are using each other in the interface part. This is only allowed
in the \var{implementation} part. At least one unit must contain the other one in the \var{implementation} part. At least one unit must contain the other one
in the \var{implementation} section. in the \var{implementation} section.
@ -948,7 +1037,40 @@
\item [Fatal: There were arg1 errors compiling module, stopping] \item [Fatal: There were arg1 errors compiling module, stopping]
When the compiler encounters a fatal error or too many errors in a module When the compiler encounters a fatal error or too many errors in a module
then it stops with this message. then it stops with this message.
\end{description} \item [Load from arg1 (arg2) unit arg3]
When you use the \var{-vu} flag, which unit is loaded from which unit is
shown.
\item [Recompiling arg1, checksum changed for arg2]
\item [Recompiling arg1, source found only]
When you use the \var{-vu} flag, these messages tell you why the current
unit is recompiled.
\item [Recompiling unit, static lib is older than ppufile]
When you use the \var{-vu} flag, the compiler warns if the static library
of the unit are older than the unit file itself.
\item [Recompiling unit, shared lib is older than ppufile]
When you use the \var{-vu} flag, the compiler warns if the shared library
of the unit are older than the unit file itself.
\item [Recompiling unit, obj and asm are older than ppufile]
When you use the \var{-vu} flag, the compiler warns if the assembler of
object file of the unit are older than the unit file itself.
\item [Recompiling unit, obj is older than asm]
When you use the \var{-vu} flag, the compiler warns if the assembler
file of the unit is older than the object file of the unit.
\item [Parsing interface of arg1]
When you use the \var{-vu} flag, the compiler warns that it starts
parsing the interface part of the unit
\item [Parsing implementation of arg1]
When you use the \var{-vu} flag, the compiler warns that it starts
parsing the implementation part of the unit
\item [Second load for unit arg1]
When you use the \var{-vu} flag, the compiler warns that it starts
recompiling a unit for the second time. This can happend with interdepend
units.
\item [PPU Check file arg1 time arg2]
When you use the \var{-vu} flag, the compiler show the filename and
date and time of the file which a recompile depends on
\end{description}
\section{Command-line handling errors} \section{Command-line handling errors}
This section lists errors that occur when the compiler is processing the This section lists errors that occur when the compiler is processing the
command line or handling the configuration files. command line or handling the configuration files.
@ -996,4 +1118,8 @@
It is possible to have a compiler executable that doesn't support It is possible to have a compiler executable that doesn't support
the generation of debugging info. If you use such an executable with the the generation of debugging info. If you use such an executable with the
\var{-g} switch, this warning will be displayed. \var{-g} switch, this warning will be displayed.
\end{description} \item [Warning: You are using the obsolete switch arg1]
this warns you when you use a switch that is not needed/supported anymore.
It is recommended that you remove the switch to overcome problems in the
future, when the switch meaning may change.
\end{description}