#### /compiler/msg/errore.msg

https://github.com/slibre/freepascal
Unknown | 3661 lines | 3633 code | 28 blank | 0 comment | 0 complexity | 18609f6083c110e6853ea308d7194922 MD5 | raw file

Large files files are truncated, but you can click here to view the full file

  1#
2#   This file is part of the Free Pascal Compiler
3#   Copyright (c) 1999-2009 by the Free Pascal Development team
4#
6#
7#   See the file COPYING.v2, included in this distribution,
9#
10#   This program is distributed in the hope that it will be useful,
11#   but WITHOUT ANY WARRANTY; without even the implied warranty of
12#   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
13#
14#
15# The constants are build in the following order:
16# <part>_<type>_<txtidentifier>
17#
18# <part> is the part of the compiler the message is used
19#   asmr_     assembler parsing
20#   asmw_     assembler writing/binary writers
21#   unit_     unit handling
22#   option_   command line parameter parsing
23#   scan_     scanner
24#   parser_   parser
25#   type_     type checking
26#   general_  general info
27#   exec_     calls to assembler, external linker, binder
29#
30# <type> the type of the message it should normally used for
31#   f_   fatal error
32#   e_   error
33#   w_   warning
34#   n_   note
35#   h_   hint
36#   i_   info
38#   u_   used
39#   t_   tried
40#   c_   conditional
41#   d_   debug message
42#   x_   executable informations
43#   o_   normal (e.g., "press enter to continue")
44#
45# <type> can contain a minus sign at the beginning to mark that
46# the message is off by default. Look at type_w_explicit_string_cast
47# for example.
48
49#
50# General
51#
52# 01023 is the last used one
53#
54# BeginOfTeX
55% \section{General compiler messages}
56% This section gives the compiler messages which are not fatal, but which
57% display useful information. The number of such messages can be
58% controlled with the various verbosity level \var{-v} switches.
59% \begin{description}
60general_t_compilername=01000_T_Compiler: $1 61% When the \var{-vt} switch is used, this line tells you what compiler 62% is used. 63general_d_sourceos=01001_D_Compiler OS:$1
64% When the \var{-vd} switch is used, this line tells you what the source
65% operating system is.
66general_i_targetos=01002_I_Target OS: $1 67% When the \var{-vd} switch is used, this line tells you what the target 68% operating system is. 69general_t_exepath=01003_T_Using executable path:$1
70% When the \var{-vt} switch is used, this line tells you where the compiler
71% looks for its binaries.
72general_t_unitpath=01004_T_Using unit path: $1 73% When the \var{-vt} switch is used, this line tells you where the compiler 74% looks for compiled units. You can set this path with the \var{-Fu} option. 75general_t_includepath=01005_T_Using include path:$1
76% When the \var{-vt} switch is used, this line tells you where the compiler
77% looks for its include files (files used in \var{\{\$I xxx\}} statements). 78% You can set this path with the \var{-Fi} option. 79general_t_librarypath=01006_T_Using library path:$1
80% When the \var{-vt} switch is used, this line tells you where the compiler
81% looks for the libraries. You can set this path with the \var{-Fl} option.
82general_t_objectpath=01007_T_Using object path: $1 83% When the \var{-vt} switch is used, this line tells you where the compiler 84% looks for object files you link in (files used in \var{\{\$L xxx\}} statements).
85% You can set this path with the \var{-Fo} option.
86general_i_abslines_compiled=01008_I_$1 lines compiled,$2 sec$3 87% When the \var{-vi} switch is used, the compiler reports the number 88% of lines compiled, and the time it took to compile them (real time, 89% not program time). 90general_f_no_memory_left=01009_F_No memory left 91% The compiler doesn't have enough memory to compile your program. There are 92% several remedies for this: 93% \begin{itemize} 94% \item If you're using the build option of the compiler, try compiling the 95% different units manually. 96% \item If you're compiling a huge program, split it up into units, and compile 97% these separately. 98% \item If the previous two don't work, recompile the compiler with a bigger 99% heap. (You can use the \var{-Ch} option for this, \seeo{Ch}.) 100% \end{itemize} 101general_i_writingresourcefile=01010_I_Writing Resource String Table file:$1
102% This message is shown when the compiler writes the Resource String Table
103% file containing all the resource strings for a program.
104general_e_errorwritingresourcefile=01011_E_Writing Resource String Table file: $1 105% This message is shown when the compiler encounters an error when writing 106% the Resource String Table file. 107general_i_fatal=01012_I_Fatal: 108% Prefix for Fatal Errors. 109general_i_error=01013_I_Error: 110% Prefix for Errors. 111general_i_warning=01014_I_Warning: 112% Prefix for Warnings. 113general_i_note=01015_I_Note: 114% Prefix for Notes. 115general_i_hint=01016_I_Hint: 116% Prefix for Hints. 117general_e_path_does_not_exist=01017_E_Path "$1" does not exist
118% The specified path does not exist.
119general_f_compilation_aborted=01018_F_Compilation aborted
120% Compilation was aborted.
121general_text_bytes_code=01019_bytes code
122% The size of the generated executable code, in bytes.
123general_text_bytes_data=01020_bytes data
124% The size of the generated program data, in bytes.
125general_i_number_of_warnings=01021_I_$1 warning(s) issued 126% Total number of warnings issued during compilation. 127general_i_number_of_hints=01022_I_$1 hint(s) issued
128% Total number of hints issued during compilation.
129general_i_number_of_notes=01023_I_$1 note(s) issued 130% Total number of notes issued during compilation. 131general_f_ioerror=01024_F_I/O error:$1
132% During compilation an I/O error happened which allows no further compilation.
133general_f_oserror=01025_F_Operating system error: $1 134% During compilation an operanting system error happened which allows no further compilation. 135% \end{description} 136# 137# Scanner 138# 139# 02091 is the last used one 140# 141% \section{Scanner messages.} 142% This section lists the messages that the scanner emits. The scanner takes 143% care of the lexical structure of the pascal file, i.e. it tries to find 144% reserved words, strings, etc. It also takes care of directives and 145% conditional compilation handling. 146% \begin{description} 147scan_f_end_of_file=02000_F_Unexpected end of file 148% This typically happens in one of the following cases: 149% \begin{itemize} 150% \item The source file ends before the final \var{end.} statement. This 151% happens mostly when the \var{begin} and \var{end} statements aren't 152% balanced; 153% \item An include file ends in the middle of a statement. 154% \item A comment was not closed. 155% \end{itemize} 156scan_f_string_exceeds_line=02001_F_String exceeds line 157% There is a missing closing ' in a string, so it occupies 158% multiple lines. 159scan_f_illegal_char=02002_F_illegal character "$1" ($2) 160% An illegal character was encountered in the input file. 161scan_f_syn_expected=02003_F_Syntax error, "$1" expected but "$2" found 162% This indicates that the compiler expected a different token than 163% the one you typed. It can occur almost anywhere it is possible to make an error 164% against the Pascal language. 165scan_t_start_include_file=02004_TL_Start reading includefile$1
166% When you provide the \var{-vt} switch, the compiler tells you
167% when it starts reading an included file.
168scan_w_comment_level=02005_W_Comment level $1 found 169% When the \var{-vw} switch is used, then the compiler warns you if 170% it finds nested comments. Nested comments are not allowed in Turbo Pascal 171% and Delphi, and can be a possible source of errors. 172scan_n_ignored_switch=02008_N_Ignored compiler switch "$1"
173% With \var{-vn} on, the compiler warns if it ignores a switch.
174scan_w_illegal_switch=02009_W_Illegal compiler switch "$1" 175% You included a compiler switch (i.e. \var{\{\$... \}}) which the compiler
176% does not recognise.
177scan_w_switch_is_global=02010_W_Misplaced global compiler switch
178% The compiler switch is misplaced, and should be located at
179% the start of the unit or program.
180scan_e_illegal_char_const=02011_E_Illegal char constant
181% This happens when you specify a character with its ASCII code, as in
182% \var{\#96}, but the number is either illegal, or out of range.
183scan_f_cannot_open_input=02012_F_Can't open file "$1" 184% \fpc cannot find the program or unit source file you specified on the 185% command line. 186scan_f_cannot_open_includefile=02013_F_Can't open include file "$1"
187% \fpc cannot find the source file you specified in a \var{\{\include ..\}} 188% statement. 189scan_e_illegal_pack_records=02015_E_Illegal record alignment specifier "1"
190% You are specifying \var{\{\$PACKRECORDS n\} } or \var{\{\$ALIGN n\} }
191% with an illegal value for \var{n}. For \PACKRECORDS valid alignments are 1, 2, 4, 8, 16, 32, C, 192% NORMAL, DEFAULT, and for \ALIGN valid alignments are 1, 2, 4, 8, 16, 32, ON,
193% OFF. Under mode MacPas \$ALIGN also supports MAC68K, POWER and RESET. 194scan_e_illegal_pack_enum=02016_E_Illegal enum minimum-size specifier "$1"
195% You are specifying the \var{\{\$PACKENUM n\}} with an illegal value for 196% \var{n}. Only 1,2,4, NORMAL or DEFAULT is valid here. 197scan_e_endif_expected=02017_E_$ENDIF expected for $1$2 defined in $3 line$4
198% Your conditional compilation statements are unbalanced.
199scan_e_preproc_syntax_error=02018_E_Syntax error while parsing a conditional compiling expression
200% There is an error in the expression following the \var{\{\$if ..\}}, \var{\{\$ifc \}}
201% or \var{\{\$setc \}} compiler directives. 202scan_e_error_in_preproc_expr=02019_E_Evaluating a conditional compiling expression 203% There is an error in the expression following the \var{\{\$if ..\}}, $ifc or$setc compiler
204% directives.
205scan_w_macro_cut_after_255_chars=02020_W_Macro contents are limited to 255 characters in length
206% The contents of macros cannot be longer than 255 characters.
207scan_e_endif_without_if=02021_E_ENDIF without IF(N)DEF
208% Your \var{\{\$IFDEF ..\}} and {\{\$ENDIF\}} statements aren't balanced.
209scan_f_user_defined=02022_F_User defined: $1 210% A user defined fatal error occurred. See also the \progref. 211scan_e_user_defined=02023_E_User defined:$1
213scan_w_user_defined=02024_W_User defined: $1 214% A user defined warning occurred. See also the \progref. 215scan_n_user_defined=02025_N_User defined:$1
217scan_h_user_defined=02026_H_User defined: $1 218% A user defined hint was encountered. See also the \progref. 219scan_i_user_defined=02027_I_User defined:$1
221scan_e_keyword_cant_be_a_macro=02028_E_Keyword redefined as macro has no effect
222% You cannot redefine keywords with macros.
223scan_f_macro_buffer_overflow=02029_F_Macro buffer overflow while reading or expanding a macro
224% Your macro or its result was too long for the compiler.
225scan_w_macro_too_deep=02030_W_Expanding of macros exceeds a depth of 16.
226% When expanding a macro, macros have been nested to a level of 16.
227% The compiler will expand no further, since this may be a sign that
228% recursion is used.
229scan_w_wrong_styled_switch=02031_W_compiler switches aren't supported in // styled comments
230% Compiler switches should be in normal Pascal style comments.
231scan_d_handling_switch=02032_DL_Handling switch "$1" 232% When you set debugging info on (\var{-vd}) the compiler tells you when it 233% is evaluating conditional compile statements. 234scan_c_endif_found=02033_CL_ENDIF$1 found
235% When you turn on conditional messages (\var{-vc}), the compiler tells you
236% where it encounters conditional statements.
237scan_c_ifdef_found=02034_CL_IFDEF $1 found,$2
238% When you turn on conditional messages (\var{-vc}), the compiler tells you
239% where it encounters conditional statements.
240scan_c_ifopt_found=02035_CL_IFOPT $1 found,$2
241% When you turn on conditional messages (\var{-vc}), the compiler tells you
242% where it encounters conditional statements.
243scan_c_if_found=02036_CL_IF $1 found,$2
244% When you turn on conditional messages (\var{-vc}), the compiler tells you
245% where it encounters conditional statements.
246scan_c_ifndef_found=02037_CL_IFNDEF $1 found,$2
247% When you turn on conditional messages (\var{-vc}), the compiler tells you
248% where it encounters conditional statements.
249scan_c_else_found=02038_CL_ELSE $1 found,$2
250% When you turn on conditional messages (\var{-vc}), the compiler tells you
251% where it encounters conditional statements.
252scan_c_skipping_until=02039_CL_Skipping until...
253% When you turn on conditional messages (\var{-vc}), the compiler tells you
254% where it encounters conditional statements, and whether it is skipping or
255% compiling parts.
256scan_i_press_enter=02040_I_Press <return> to continue
257% When the \var{-vi} switch is used, the compiler stops compilation
258% and waits for the \var{Enter} key to be pressed when it encounters
259% a \var{\{\$STOP\}} directive. 260scan_w_unsupported_switch=02041_W_Unsupported switch "$1"
261% When warnings are turned on (\var{-vw}), the compiler warns you about
262% unsupported switches. This means that the switch is used in Delphi or
263% Turbo Pascal, but not in \fpc.
264scan_w_illegal_directive=02042_W_Illegal compiler directive "$1" 265% When warnings are turned on (\var{-vw}), the compiler warns you about 266% unrecognised switches. For a list of recognised switches, see the \progref. 267scan_t_back_in=02043_TL_Back in$1
268% When you use the \var{-vt} switch, the compiler tells you when it has finished
270scan_w_unsupported_app_type=02044_W_Unsupported application type: "$1" 271% You get this warning if you specify an unknown application type 272% with the directive \var{\{\$APPTYPE\}}.
273scan_w_app_type_not_support=02045_W_APPTYPE is not supported by the target OS
274% The \var{\{\$APPTYPE\}} directive is supported by certain operating systems only. 275scan_w_description_not_support=02046_W_DESCRIPTION is not supported by the target OS 276% The \var{\{\$DESCRIPTION\}} directive is not supported on this target OS.
277scan_n_version_not_support=02047_N_VERSION is not supported by target OS
278% The \var{\{\$VERSION\}} directive is not supported on this target OS. 279scan_n_only_exe_version=02048_N_VERSION only for exes or DLLs 280% The \var{\{\$VERSION\}} directive is only used for executable or DLL sources.
281scan_w_wrong_version_ignored=02049_W_Wrong format for VERSION directive "$1" 282% The \var{\{\$VERSION\}} directive format is majorversion.minorversion
283% where majorversion and minorversion are words.
284scan_e_illegal_asmmode_specifier=02050_E_Illegal assembler style specified "$1" 285% When you specify an assembler mode with the \var{\{\$ASMMODE xxx\}} directive,
286% the compiler didn't recognize the mode you specified.
287scan_w_no_asm_reader_switch_inside_asm=02051_W_ASM reader switch is not possible inside asm statement, "$1" will be effective only for next 288% It is not possible to switch from one assembler reader to another 289% inside an assembler block. The new reader will be used for next 290% assembler statements only. 291scan_e_wrong_switch_toggle=02052_E_Wrong switch toggle, use ON/OFF or +/- 292% You need to use ON or OFF or a + or - to toggle the switch. 293scan_e_resourcefiles_not_supported=02053_E_Resource files are not supported for this target 294% The target you are compiling for doesn't support resource files. 295scan_w_include_env_not_found=02054_W_Include environment "$1" not found in environment
296% The included environment variable can't be found in the environment; it will
297% be replaced by an empty string instead.
298scan_e_invalid_maxfpureg_value=02055_E_Illegal value for FPU register limit
299% Valid values for this directive are 0..8 and NORMAL/DEFAULT.
300scan_w_only_one_resourcefile_supported=02056_W_Only one resource file is supported for this target
301% The target you are compiling for supports only one resource file.
302% The first resource file found is used, the others are discarded.
303scan_w_macro_support_turned_off=02057_W_Macro support has been turned off
304% A macro declaration has been found, but macro support is currently off,
305% so the declaration will be ignored. To turn macro support on compile with
306% -Sm on the command line or add \{\$MACRO ON\} in the source. 307scan_e_invalid_interface_type=02058_E_Illegal interface type specified. Valids are COM, CORBA or DEFAULT. 308% The interface type that was specified is not supported. 309scan_w_appid_not_support=02059_W_APPID is only supported for PalmOS 310% The \var{\{\$APPID\}} directive is only supported for the PalmOS target.
311scan_w_appname_not_support=02060_W_APPNAME is only supported for PalmOS
312% The \var{\{\$APPNAME\}} directive is only supported for the PalmOS target. 313scan_e_string_exceeds_255_chars=02061_E_Constant strings can't be longer than 255 chars 314% A single string constant can contain at most 255 chars. Try splitting up the 315% string into multiple smaller parts and concatenate them with a + operator. 316scan_f_include_deep_ten=02062_F_Including include files exceeds a depth of 16. 317% When including include files the files have been nested to a level of 16. 318% The compiler will expand no further, since this may be a sign that 319% recursion is used. 320scan_e_too_many_push=02063_F_Too many levels of PUSH 321% A maximum of 20 levels is allowed. This error occurs only in mode MacPas. 322scan_e_too_many_pop=02064_E_A POP without a preceding PUSH 323% This error occurs only in mode MacPas. 324scan_e_error_macro_lacks_value=02065_E_Macro or compile time variable "$1" does not have any value
325% Thus the conditional compile time expression cannot be evaluated.
326scan_e_wrong_switch_toggle_default=02066_E_Wrong switch toggle, use ON/OFF/DEFAULT or +/-/*
327% You need to use ON or OFF or DEFAULT or a + or - or * to toggle the switch.
328scan_e_mode_switch_not_allowed=02067_E_Mode switch "$1" not allowed here 329% A mode switch has already been encountered, or, in the case of option -Mmacpas, 330% a mode switch occurs after UNIT. 331scan_e_error_macro_undefined=02068_E_Compile time variable or macro "$1" is not defined.
332% Thus the conditional compile time expression cannot be evaluated. Only in mode MacPas.
333scan_e_utf8_bigger_than_65535=02069_E_UTF-8 code greater than 65535 found
334% \fpc handles UTF-8 strings internally as widestrings, i.e. the char codes are limited to 65535.
335scan_e_utf8_malformed=02070_E_Malformed UTF-8 string
336% The given string isn't a valid UTF-8 string.
337scan_c_switching_to_utf8=02071_C_UTF-8 signature found, using UTF-8 encoding
338% The compiler found a UTF-8 encoding signature (\$ef, \$bb, \$bf) at the beginning of a file, 339% so it interprets it as a UTF-8 file. 340scan_e_compile_time_typeerror=02072_E_Compile time expression: Wanted$1 but got $2 at$3
341% The type-check of a compile time expression failed.
342scan_n_app_type_not_support=02073_N_APPTYPE is not supported by the target OS
343% The \var{\{\$APPTYPE\}} directive is supported by certain operating systems only. 344scan_e_illegal_optimization_specifier=02074_E_Illegal optimization specified "$1"
345% You specified an optimization with the \var{\{\$OPTIMIZATION xxx\}} directive, 346% and the compiler didn't recognize the optimization you specified. 347scan_w_setpeflags_not_support=02075_W_SETPEFLAGS is not supported by the target OS 348% The \var{\{\$SETPEFLAGS\}} directive is not supported by the target OS.
349scan_w_imagebase_not_support=02076_W_IMAGEBASE is not supported by the target OS
350% The \var{\{\$IMAGEBASE\}} directive is not supported by the target OS. 351scan_w_minstacksize_not_support=02077_W_MINSTACKSIZE is not supported by the target OS 352% The \var{\{\$MINSTACKSIZE\}} directive is not supported by the target OS.
353scan_w_maxstacksize_not_support=02078_W_MAXSTACKSIZE is not supported by the target OS
354% The \var{\{\$MAXSTACKSIZE\}} directive is not supported by the target OS. 355scanner_e_illegal_warn_state=02079_E_Illegal state "$1" for $WARN directive 356% Only ON and OFF can be used as state with a \var{\{\$WARN\}} compiler directive.
357scan_e_only_packset=02080_E_Illegal set packing value
358% Only 0, 1, 2, 4, 8, DEFAULT and NORMAL are allowed as packset parameters.
359scan_w_pic_ignored=02081_W_PIC directive or switch ignored
360% Several targets, such as \windows, do not support nor need PIC,
361% so the PIC directive and switch are ignored.
362scan_w_unsupported_switch_by_target=02082_W_The switch "$1" is not supported by the currently selected target 363% Some compiler switches like \$E are not supported by all targets.
364scan_w_frameworks_darwin_only=02084_W_Framework-related options are only supported for Darwin/Mac OS X
365% Frameworks are not a known concept, or at least not supported by FPC,
366% on operating systems other than Darwin/Mac OS X.
367scan_e_illegal_minfpconstprec=02085_E_Illegal minimal floating point constant precision "$1" 368% Valid minimal precisions for floating point constants are default, 32 and 64, 369% which mean respectively minimal (usually 32 bit), 32 bit and 64 bit precision. 370scan_w_multiple_main_name_overrides=02086_W_Overriding name of "main" procedure multiple times, was previously set to "$1"
371% The name for the main entry procedure is specified more than once. Only the last
372% name will be used.
373scanner_w_illegal_warn_identifier=02087_W_Illegal identifier "$1" for$WARN directive
374% Identifier is not known by a \var{\{\WARN\}} compiler directive. 375scanner_e_illegal_alignment_directive=02088_E_Illegal alignment directive 376% The alignment directive is not valid. Either the alignment type is not known or the alignment 377% value is not a power of two. 378scanner_f_illegal_utf8_bom=02089_F_It is not possible to include a file that starts with an UTF-8 BOM in a module that uses a different code page 379% All source code that is part of a single compilation entity (program, library, unit) must be encoded 380% in the same code page 381scanner_w_directive_ignored_on_target=02090_W_Directive "1" is ignored for the the current target platform
382% Some directives are ignored for certain targets, such as changing the
383% packrecords and packenum settings on managed platforms.
384scan_w_unavailable_system_codepage=02091_W_Current system codepage "$1" is not available for the compiler. Switching default codepage back to "$2".
385% The current system codepage is not known by the compiler.
386% The compiler is compiled with support for several codepages built-in.
387% The codepage of the operation system is not in that list. You will need to recompile
388% the compiler with support for this codepage.
389scan_w_setpeoptflags_not_support=02092_W_SETPEOPTFLAGS is not supported by the target OS
390% The \var{\{\$SETPEOPTFLAGS\}} directive is not supported by the target OS. 391% \end{description} 392# 393# Parser 394# 395# 03331 is the last used one 396# 397% \section{Parser messages} 398% This section lists all parser messages. The parser takes care of the 399% semantics of you language, i.e. it determines if your Pascal constructs 400% are correct. 401% \begin{description} 402parser_e_syntax_error=03000_E_Parser - Syntax Error 403% An error against the Turbo Pascal language was encountered. This typically 404% happens when an illegal character is found in the source file. 405parser_e_dont_nest_interrupt=03004_E_INTERRUPT procedure can't be nested 406% An \var{INTERRUPT} procedure must be global. 407parser_w_proc_directive_ignored=03005_W_Procedure type "$1" ignored
408% The specified procedure directive is ignored by FPC programs.
409parser_e_no_overload_for_all_procs=03006_E_Not all declarations of "$1" are declared with OVERLOAD 410% When you want to use overloading using the \var{OVERLOAD} directive, then 411% all declarations need to have \var{OVERLOAD} specified. 412parser_e_export_name_double=03008_E_Duplicate exported function name "$1"
413% Exported function names inside a specific DLL must all be different.
414parser_e_export_ordinal_double=03009_E_Duplicate exported function index $1 415% Exported function indexes inside a specific DLL must all be different. 416parser_e_export_invalid_index=03010_E_Invalid index for exported function 417% DLL function index must be in the range \var{1..\$FFFF}.
418parser_w_parser_reloc_no_debug=03011_W_Relocatable DLL or executable $1 debug info does not work, disabled. 419% It is currently not possible to include debug information in a relocatable DLL. 420parser_w_parser_win32_debug_needs_WN=03012_W_To allow debugging for win32 code you need to disable relocation with -WN option 421% Stabs debug info is wrong for relocatable DLL or EXES. Use -WN 422% if you want to debug win32 executables. 423parser_e_constructorname_must_be_init=03013_E_Constructor name must be INIT 424% You are declaring an object constructor with a name which is not \var{init}, and the 425% \var{-Ss} switch is in effect. See the switch \seeo{Ss}. 426parser_e_destructorname_must_be_done=03014_E_Destructor name must be DONE 427% You are declaring an object destructor with a name which is not \var{done}, and the 428% \var{-Ss} switch is in effect. See the switch \seeo{Ss}. 429parser_e_proc_inline_not_supported=03016_E_Procedure type INLINE not supported 430% You tried to compile a program with C++ style inlining, and forgot to 431% specify the \var{-Si} option (\seeo{Si}). The compiler doesn't support C++ 432% styled inlining by default. 433parser_w_constructor_should_be_public=03018_W_Constructor should be public 434% Constructors must be in the 'public' part of an object (class) declaration. 435parser_w_destructor_should_be_public=03019_W_Destructor should be public 436% Destructors must be in the 'public' part of an object (class) declaration. 437parser_n_only_one_destructor=03020_N_Class should have one destructor only 438% You can declare only one destructor for a class. 439parser_e_no_local_objects=03021_E_Local class definitions are not allowed 440% Classes must be defined globally. They cannot be defined inside a 441% procedure or function. 442parser_f_no_anonym_objects=03022_F_Anonymous class definitions are not allowed 443% An invalid object (class) declaration was encountered, i.e. an 444% object or class without methods that isn't derived from another object or 445% class. For example: 446% \begin{verbatim} 447% Type o = object 448% a : longint; 449% end; 450% \end{verbatim} 451% will trigger this error. 452parser_n_object_has_no_vmt=03023_N_The object "$1" has no VMT
453% This is a note indicating that the declared object has no
454% virtual method table.
455parser_e_illegal_parameter_list=03024_E_Illegal parameter list
456% You are calling a function with parameters that are of a different type than
457% the declared parameters of the function.
458parser_e_wrong_parameter_size=03026_E_Wrong number of parameters specified for call to "$1" 459% There is an error in the parameter list of the function or procedure -- 460% the number of parameters is not correct. 461parser_e_overloaded_no_procedure=03027_E_overloaded identifier "$1" isn't a function
462% The compiler encountered a symbol with the same name as an overloaded
463% function, but it is not a function it can overload.
465% You're declaring overloaded functions, but with the same parameter list.
466% Overloaded function must have at least 1 different parameter in their
467% declaration.
468parser_e_header_dont_match_forward=03029_E_function header doesn't match the previous declaration "$1" 469% You declared a function with the same parameters but 470% different result type or function modifiers. 471parser_e_header_different_var_names=03030_E_function header "$1" doesn't match forward : var name changes $2 =>$3
472% You declared the function in the \var{interface} part, or with the
473% \var{forward} directive, but defined it with a different parameter list.
474parser_n_duplicate_enum=03031_N_Values in enumeration types have to be ascending
475% \fpc allows enumeration constructions as in C. Examine the following
476% two declarations:
477% \begin{verbatim}
478% type a = (A_A,A_B,A_E:=6,A_UAS:=200);
479% type a = (A_A,A_B,A_E:=6,A_UAS:=4);
480% \end{verbatim}
481% The second declaration would produce an error. \var{A\_UAS} needs to have a
482% value higher than \var{A\_E}, i.e. at least 7.
483parser_e_no_with_for_variable_in_other_segments=03033_E_With cannot be used for variables in a different segment
484% With stores a variable locally on the stack,
485% but this is not possible if the variable belongs to another segment.
486parser_e_too_much_lexlevel=03034_E_function nesting > 31
487% You can nest function definitions only 31 levels deep.
488parser_e_range_check_error=03035_E_range check error while evaluating constants
489% The constants are out of their allowed range.
490parser_w_range_check_error=03036_W_range check error while evaluating constants
491% The constants are out of their allowed range.
492parser_e_double_caselabel=03037_E_duplicate case label
493% You are specifying the same label 2 times in a \var{case} statement.
494parser_e_case_lower_less_than_upper_bound=03038_E_Upper bound of case range is less than lower bound
495% The upper bound of a \var{case} label is less than the lower bound and this
496% is useless.
497parser_e_type_const_not_possible=03039_E_typed constants of classes or interfaces are not allowed
498% You cannot declare a constant of type class or object.
500% You are trying to assign an overloaded function to a procedural variable.
501% This is not allowed.
502parser_e_invalid_string_size=03041_E_string length must be a value from 1 to 255
503% The length of a shortstring in Pascal is limited to 255 characters. You are
504% trying to declare a string with length less than 1 or greater than 255.
505parser_w_use_extended_syntax_for_objects=03042_W_use extended syntax of NEW and DISPOSE for instances of objects
506% If you have a pointer \var{a} to an object type, then the statement
507% \var{new(a)} will not initialize the object (i.e. the constructor isn't
508% called), although space will be allocated. You should issue the
509% \var{new(a,init)} statement. This will allocate space, and call the
510% constructor of the object.
511parser_w_no_new_dispose_on_void_pointers=03043_W_use of NEW or DISPOSE for untyped pointers is meaningless
512parser_e_no_new_dispose_on_void_pointers=03044_E_use of NEW or DISPOSE is not possible for untyped pointers
513% You cannot use \var{new(p)} or \var{dispose(p)} if \var{p} is an untyped pointer
514% because no size is associated to an untyped pointer.
515% It is accepted for compatibility in \var{TP} and \var{DELPHI} modes, but the
516% compiler will still warn you if it finds such a construct.
517parser_e_class_id_expected=03045_E_class identifier expected
518% This happens when the compiler scans a procedure declaration that contains
519% a dot, i.e., an object or class method, but the type in front of the dot is not
520% a known type.
521parser_e_no_type_not_allowed_here=03046_E_type identifier not allowed here
522% You cannot use a type inside an expression.
523parser_e_methode_id_expected=03047_E_method identifier expected
524% This identifier is not a method.
525% This happens when the compiler scans a procedure declaration that contains
526% a dot, i.e., an object or class method, but the procedure name is not a
527% procedure of this type.
528parser_e_header_dont_match_any_member=03048_E_function header doesn't match any method of this class "$1" 529% This identifier is not a method. 530% This happens when the compiler scans a procedure declaration that contains 531% a dot, i.e., an object or class method, but the procedure name is not a 532% procedure of this type. 533parser_d_procedure_start=03049_DL_procedure/function$1
534% When using the \var{-vd} switch, the compiler tells you when it starts
535% processing a procedure or function implementation.
536parser_e_error_in_real=03050_E_Illegal floating point constant
537% The compiler expects a floating point expression, and gets something else.
538parser_e_fail_only_in_constructor=03051_E_FAIL can be used in constructors only
539% You are using the \var{fail} keyword outside a constructor method.
540parser_e_no_paras_for_destructor=03052_E_Destructors can't have parameters
541% You are declaring a destructor with a parameter list. Destructor methods
542% cannot have parameters.
543parser_e_only_class_members_via_class_ref=03053_E_Only class methods, class properties and class variables can be referred with class references
544% This error occurs in a situation like the following:
545% \begin{verbatim}
546% Type :
547%    Tclass = Class of Tobject;
548%
549% Var C : TClass;
550%
551% begin
552% ...
553% C.free
554% \end{verbatim}
555% \var{Free} is not a class method and hence cannot be called with a class
556% reference.
557parser_e_only_class_members=03054_E_Only class methods, class properties and class variables can be accessed in class methods
558% This is related to the previous error. You cannot call a method of an object
559% from inside a class method. The following code would produce this error:
560% \begin{verbatim}
561% class procedure tobject.x;
562%
563% begin
564%   free
565% \end{verbatim}
566% Because free is a normal method of a class it cannot be called from a class
567% method.
568parser_e_case_mismatch=03055_E_Constant and CASE types do not match
569% One of the labels is not of the same type as the case variable.
570parser_e_illegal_symbol_exported=03056_E_The symbol can't be exported from a library
571% You can only export procedures and functions when you write a library. You
572% cannot export variables or constants.
573parser_w_should_use_override=03057_W_An inherited method is hidden by "$1" 574% A method that is declared \var{virtual} in a parent class, should be 575% overridden in the descendant class with the \var{override} directive. If you 576% don't specify the \var{override} directive, you will hide the parent method; 577% you will not override it. 578parser_e_nothing_to_be_overridden=03058_E_There is no method in an ancestor class to be overridden: "$1"
579% You are trying to \var{override} a virtual method of a parent class that does
580% not exist.
581parser_e_no_procedure_to_access_property=03059_E_No member is provided to access property
582% You specified no \var{read} directive for a property.
583parser_w_stored_not_implemented=03060_W_Stored property directive is not yet implemented
584% This message is no longer used, as the \var{stored} directive has been implemented.
585parser_e_ill_property_access_sym=03061_E_Illegal symbol for property access
586% There is an error in the \var{read} or \var{write} directives for an array
587% property. When you declare an array property, you can only access it with
588% procedures and functions. The following code would cause such an error.
589% \begin{verbatim}
590% tmyobject = class
591%   i : integer;
592%   property x [i : integer]: integer read I write i;
593% \end{verbatim}
594%
595parser_e_cant_access_protected_member=03062_E_Cannot access a protected field of an object here
596% Fields that are declared in a \var{protected} section of an object or class
597% declaration cannot be accessed outside the module where the object is
598% defined, or outside descendent object methods.
599parser_e_cant_access_private_member=03063_E_Cannot access a private field of an object here
600% Fields that are declared in a \var{private} section of an object or class
601% declaration cannot be accessed outside the module where the class is
602% defined.
603parser_e_overridden_methods_not_same_ret=03066_E_Overridden methods must have the same return type: "$2" is overridden by "$1" which has another return type
604% If you declare overridden methods in a class definition, they must
605% have the same return type.
606parser_e_dont_nest_export=03067_E_EXPORT declared functions can't be nested
607% You cannot declare a function or procedure within a function or procedure
608% that was declared as an export procedure.
609parser_e_methods_dont_be_export=03068_E_Methods can't be EXPORTed
610% You cannot declare a procedure that is a method for an object as
611% \var{export}ed.
612parser_e_call_by_ref_without_typeconv=03069_E_Call by var for arg no. $1 has to match exactly: Got "$2" expected "$3" 613% When calling a function declared with \var{var} parameters, the variables in 614% the function call must be of exactly the same type. There is no automatic 615% type conversion. 616parser_e_no_super_class=03070_E_Class isn't a parent class of the current class 617% When calling inherited methods, you are trying to call a method of a non-related 618% class. You can only call an inherited method of a parent class. 619parser_e_self_not_in_method=03071_E_SELF is only allowed in methods 620% You are trying to use the \var{self} parameter outside an object's method. 621% Only methods get passed the \var{self} parameters. 622parser_e_generic_methods_only_in_methods=03072_E_Methods can be only in other methods called direct with type identifier of the class 623% A construction like \var{sometype.somemethod} is only allowed in a method. 624parser_e_illegal_colon_qualifier=03073_E_Illegal use of ':' 625% You are using the format \var{:} (colon) 2 times on an expression that 626% is not a real expression. 627parser_e_illegal_set_expr=03074_E_range check error in set constructor or duplicate set element 628% The declaration of a set contains an error. Either one of the elements is 629% outside the range of the set type, or two of the elements are in fact 630% the same. 631parser_e_pointer_to_class_expected=03075_E_Pointer to object expected 632% You specified an illegal type in a \var{new} statement. 633% The extended syntax of \var{new} needs an object as a parameter. 634parser_e_expr_have_to_be_constructor_call=03076_E_Expression must be constructor call 635% When using the extended syntax of \var{new}, you must specify the constructor 636% method of the object you are trying to create. The procedure you specified 637% is not a constructor. 638parser_e_expr_have_to_be_destructor_call=03077_E_Expression must be destructor call 639% When using the extended syntax of \var{dispose}, you must specify the 640% destructor method of the object you are trying to dispose of. 641% The procedure you specified is not a destructor. 642parser_e_invalid_record_const=03078_E_Illegal order of record elements 643% When declaring a constant record, you specified the fields in the wrong 644% order. 645parser_e_false_with_expr=03079_E_Expression type must be class or record type, got$1
646% A \var{with} statement needs an argument that is of the type \var{record}
647% or \var{class}. You are using \var{with} on an expression that is not of
648% this type.
649parser_e_void_function=03080_E_Procedures can't return a value
650% In \fpc, you can specify a return value for a function when using
651% the \var{exit} statement. This error occurs when you try to do this with a
652% procedure. Procedures cannot return a value.
653parser_e_only_methods_allowed=03081_E_constructors, destructors and class operators must be methods
654% You're declaring a procedure as destructor, constructor or class operator, when the
655% procedure isn't a class method.
657% You're trying to use an overloaded operator when it is not overloaded for
658% this type.
659parser_e_no_such_assignment=03083_E_Impossible to overload assignment for equal types
660% You cannot overload assignment for types
661% that the compiler considers as equal.
663% The combination of operator, arguments and return type are
664% incompatible.
665parser_e_no_reraise_possible=03085_E_Re-raise isn't possible there
666% You are trying to re-raise an exception where it is not allowed. You can only
667% re-raise exceptions in an \var{except} block.
668parser_e_no_new_or_dispose_for_classes=03086_E_The extended syntax of new or dispose isn't allowed for a class
669% You cannot generate an instance of a class with the extended syntax of
670% \var{new}. The constructor must be used for that. For the same reason, you
671% cannot call \var{dispose} to de-allocate an instance of a class, the
672% destructor must be used for that.
676parser_e_overload_operator_failed=03089_E_It is not possible to overload this operator. Related overloadable operators (if any) are: $1 677% You are trying to overload an operator which cannot be overloaded. 678% The following operators can be overloaded : 679% \begin{verbatim} 680% +, -, *, /, =, >, <, <=, >=, is, as, in, **, := 681% \end{verbatim} 682parser_e_comparative_operator_return_boolean=03090_E_Comparative operator must return a boolean value 683% When overloading the \var{=} operator, the function must return a boolean 684% value. 685parser_e_only_virtual_methods_abstract=03091_E_Only virtual methods can be abstract 686% You are declaring a method as abstract, when it is not declared to be 687% virtual. 688parser_f_unsupported_feature=03092_F_Use of unsupported feature! 689% You're trying to force the compiler into doing something it cannot do yet. 690parser_e_mix_of_classes_and_objects=03093_E_The mix of different kind of objects (class, object, interface, etc) isn't allowed 691% You cannot derive \var{objects}, \var{classes}, \var{cppclasses} and \var{interfaces} intertwined. E.g. 692% a class cannot have an object as parent and vice versa. 693parser_w_unknown_proc_directive_ignored=03094_W_Unknown procedure directive had to be ignored: "$1"
694% The procedure directive you specified is unknown.
695parser_e_directive_only_one_var=03095_E_$1 can be associated with only one variable 696% You cannot specify more than one variable before the \var{absolute}, \var{export}, \var{external}, 697% \var{weakexternal}, \var{public} and \var{cvar} directives. 698% As a result, for example the following construct will provide this error: 699% \begin{verbatim} 700% Var Z : Longint; 701% X,Y : Longint absolute Z; 702% \end{verbatim} 703parser_e_absolute_only_to_var_or_const=03096_E_absolute can only be associated with a var or const 704% The address of an \var{absolute} directive can only point to a variable or 705% constant. Therefore, the following code will produce this error: 706% \begin{verbatim} 707% Procedure X; 708% 709% var p : longint absolute x; 710% \end{verbatim} 711parser_e_initialized_only_one_var=03097_E_Only one variable can be initialized 712% You cannot specify more than one variable with a initial value in Delphi mode. 713parser_e_abstract_no_definition=03098_E_Abstract methods shouldn't have any definition (with function body) 714% Abstract methods can only be declared, you cannot implement them. They 715% should be overridden by a descendant class. 716parser_e_overloaded_must_be_all_global=03099_E_This overloaded function can't be local (must be exported) 717% You are defining an overloaded function in the implementation part of a unit, 718% but there is no corresponding declaration in the interface part of the unit. 719parser_w_virtual_without_constructor=03100_W_Virtual methods are used without a constructor in "$1"
720% If you declare objects or classes that contain virtual methods, you need
721% to have a constructor and destructor to initialize them. The compiler
722% encountered an object or class with virtual methods that doesn't have
723% a constructor/destructor pair.
724parser_c_macro_defined=03101_CL_Macro defined: $1 725% When \var{-vc} is used, the compiler tells you when it defines macros. 726parser_c_macro_undefined=03102_CL_Macro undefined:$1
727% When \var{-vc} is used, the compiler tells you when it undefines macros.
728parser_c_macro_set_to=03103_CL_Macro $1 set to$2
729% When \var{-vc} is used, the compiler tells you what values macros get.
730parser_i_compiling=03104_I_Compiling $1 731% When you turn on information messages (\var{-vi}), the compiler tells you 732% what units it is recompiling. 733parser_u_parsing_interface=03105_UL_Parsing interface of unit$1
734% This tells you that the reading of the interface
735% of the current unit has started
736parser_u_parsing_implementation=03106_UL_Parsing implementation of $1 737% This tells you that the code reading of the implementation 738% of the current unit, library or program starts 739parser_d_compiling_second_time=03107_DL_Compiling$1 for the second time
740% When you request debug messages (\var{-vd}) the compiler tells you what
741% units it recompiles for the second time.
742parser_e_no_property_found_to_override=03109_E_No property found to override
743% You want to override a property of a parent class, when there is, in fact,
744% no such property in the parent class.
745parser_e_only_one_default_property=03110_E_Only one default property is allowed
746% You specified a property as \var{Default}, but the class already has a
747% default property, and a class can have only one default property.
748parser_e_property_need_paras=03111_E_The default property must be an array property
749% Only array properties of classes can be made \var{default} properties.
750parser_e_constructor_cannot_be_not_virtual=03112_E_Virtual constructors are only supported in class object model
751% You cannot have virtual constructors in objects. You can only have them
752% in classes.
753parser_e_no_default_property_available=03113_E_No default property available
754% You are trying to access a default property of a class, but this class (or one of
755% its ancestors) doesn't have a default property.
756parser_e_cant_have_published=03114_E_The class can't have a published section, use the {$M+} switch 757% If you want a \var{published} section in a class definition, you must 758% use the \var{\{\$M+\}} switch, which turns on generation of type
759% information.
760parser_e_forward_declaration_must_be_resolved=03115_E_Forward declaration of class "$1" must be resolved here to use the class as ancestor 761% To be able to use an object as an ancestor object, it must be defined 762% first. This error occurs in the following situation: 763% \begin{verbatim} 764% Type ParentClas = Class; 765% ChildClass = Class(ParentClass) 766% ... 767% end; 768% \end{verbatim} 769% where \var{ParentClass} is declared but not defined. 770parser_e_no_local_operator=03116_E_Local operators not supported 771% You cannot overload locally, i.e. inside procedures or function 772% definitions. 773parser_e_proc_dir_not_allowed_in_interface=03117_E_Procedure directive "$1" not allowed in interface section
774% This procedure directive is not allowed in the \var{interface} section of
775% a unit. You can only use it in the \var{implementation} section.
776parser_e_proc_dir_not_allowed_in_implementation=03118_E_Procedure directive "$1" not allowed in implementation section 777% This procedure directive is not allowed in the \var{implementation} section of 778% a unit. You can only use it in the \var{interface} section. 779parser_e_proc_dir_not_allowed_in_procvar=03119_E_Procedure directive "$1" not allowed in procvar declaration
780% This procedure directive cannot be part of a procedural or function
781% type declaration.
782parser_e_function_already_declared_public_forward=03120_E_Function is already declared Public/Forward "$1" 783% You will get this error if a function is defined as \var{forward} twice. 784% Or if it occurs in the \var{interface} section, and again as a \var{forward} 785% declaration in the \var{implementation} section. 786parser_e_not_external_and_export=03121_E_Can't use both EXPORT and EXTERNAL 787% These two procedure directives are mutually exclusive. 788parser_h_not_supported_for_inline=03123_H_"$1" not yet supported inside inline procedure/function
789% Inline procedures don't support this declaration.
790parser_h_inlining_disabled=03124_H_Inlining disabled
791% Inlining of procedures is disabled.
792parser_i_writing_browser_log=03125_I_Writing Browser log $1 793% When information messages are on, the compiler warns you when it 794% writes the browser log (generated with the \var{\{\$Y+ \}} switch).
795parser_h_maybe_deref_caret_missing=03126_H_may be pointer dereference is missing
796% The compiler thinks that a pointer may need a dereference.
798% The selected assembler reader (with \var{\{\$ASMMODE xxx\}} is not 799% supported. The compiler can be compiled with or without support for a 800% particular assembler reader. 801parser_e_proc_dir_conflict=03128_E_Procedure directive "$1" has conflicts with other directives
802% You specified a procedure directive that conflicts with other directives.
803% For instance \var{cdecl} and \var{pascal} are mutually exclusive.
804parser_e_call_convention_dont_match_forward=03129_E_Calling convention doesn't match forward
805% This error happens when you declare a function or procedure with
806% e.g. \var{cdecl;} but omit this directive in the implementation, or vice
807% versa. The calling convention is part of the function declaration, and
808% must be repeated in the function definition.
809parser_e_property_cant_have_a_default_value=03131_E_Property can't have a default value
810% Set properties or indexed properties cannot have a default value.
811parser_e_property_default_value_must_const=03132_E_The default value of a property must be constant
812% The value of a \var{default} declared property must be known at compile
813% time. The value you specified is only known at run time. This happens
814% e.g. if you specify a variable name as a default value.
815parser_e_cant_publish_that=03133_E_Symbol can't be published, can be only a class
816% Only class type variables can be in a \var{published} section of a class
817% if they are not declared as a property.
818parser_e_cant_publish_that_property=03134_E_This kind of property can't be published
819% Properties in a \var{published} section cannot be array properties.
820% They must be moved to public sections. Properties in a \var{published}
821% section must be an ordinal type, a real type, strings or sets.
822parser_e_empty_import_name=03136_E_An import name is required
823% Some targets need a name for the imported procedure or a \var{cdecl} specifier.
824parser_e_division_by_zero=03138_E_Division by zero
825% A division by zero was encounted.
826parser_e_invalid_float_operation=03139_E_Invalid floating point operation
827% An operation on two real type values produced an overflow or a division
828% by zero.
829parser_e_array_lower_less_than_upper_bound=03140_E_Upper bound of range is less than lower bound
830% The upper bound of an array declaration is less than the lower bound and this
831% is not possible.
832parser_w_string_too_long=03141_W_string "$1" is longer than "$2"
833% The size of the constant string is larger than the size you specified in
834% string type definition.
835parser_e_string_larger_array=03142_E_string length is larger than array of char length
836% The size of the constant string is larger than the size you specified in
837% the \var{Array[x..y] of char} definition.
838parser_e_ill_msg_expr=03143_E_Illegal expression after message directive
839% \fpc supports only integer or string values as message constants.
840parser_e_ill_msg_param=03144_E_Message handlers can take only …

Large files files are truncated, but you can click here to view the full file