/compiler/msg/errorhe.msg
Unknown | 2704 lines | 2685 code | 19 blank | 0 comment | 0 complexity | 0c8dabec5344d8c55aa3d27e299dbc48 MD5 | raw file
Possible License(s): LGPL-2.0, LGPL-2.1, LGPL-3.0
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-2008 by the Free Pascal Development team 4# 5# Hebrew (CP1255) language file for Free Pascal Compiler 6# Contributed by Ido Kanner <idokan at gmail.com> and Dotan Kamber <kamberd at yahoo.com> 7# Based on errore.msg of SVN revision 8988 8# 9# See the file COPYING.v2, included in this distribution, 10# for details about the copyright. 11# 12# This program is distributed in the hope that it will be useful, 13# but WITHOUT ANY WARRANTY; without even the implied warranty of 14# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 15# 16# 17# The constants are build in the following order: 18# <part>_<type>_<txtidentifier> 19# 20# <part> is the part of the compiler the message is used 21# asmr_ assembler parsing 22# asmw_ assembler writing/binary writers 23# unit_ unit handling 24# scan_ scanner 25# parser_ parser 26# type_ type checking 27# general_ general info 28# exec_ calls to assembler, 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 37# l_ add linenumber 38# u_ used 39# t_ tried 40# c_ conditional 41# d_ debug message 42# x_ executable informations 43# 44 45# 46# General 47# 48# 01023 is the last used one 49# 50# BeginOfTeX 51% \section{General compiler messages} 52% This section gives the compiler messages which are not fatal, but which 53% display useful information. The number of such messages can be 54% controlled with the various verbosity level \var{-v} switches. 55% \begin{description} 56general_t_compilername=01000_T_????: $1 57% When the \var{-vt} switch is used, this line tells you what compiler 58% is used. 59general_d_sourceos=01001_D_????? ?????: $1 60% When the \var{-vd} switch is used, this line tells you what the source 61% operating system is. 62general_i_targetos=01002_I_????? ????? ??????: $1 63% When the \var{-vd} switch is used, this line tells you what the target 64% operating system is. 65general_t_exepath=01003_T_????? ????? ????: $1 66% When the \var{-vt} switch is used, this line tells you where the compiler 67% looks for its binaries. 68general_t_unitpath=01004_T_????? ????? ???????: $1 69% When the \var{-vt} switch is used, this line tells you where the compiler 70% looks for compiled units. You can set this path with the \var{-Fu} 71general_t_includepath=01005_T_????? ????? ?????: $1 72% When the \var{-vt} switch is used, this line tells you where the compiler 73% looks for its include files (files used in \var{\{\$I xxx\}} statements). 74% You can set this path with the \var{-I} option. 75general_t_librarypath=01006_T_????? ????? ??????: $1 76% When the \var{-vt} switch is used, this line tells you where the compiler 77% looks for the libraries. You can set this path with the \var{-Fl} option. 78general_t_objectpath=01007_T_Using object path: $1 79% When the \var{-vt} switch is used, this line tells you where the compiler 80% looks for object files you link in (files used in \var{\{\$L xxx\}} statements). 81% You can set this path with the \var{-Fo} option. 82general_i_abslines_compiled=01008_I_$1 ????? ?????, ?$2 ????? 83% When the \var{-vi} switch is used, the compiler reports the number 84% of lines compiled, and the time it took to compile them (real time, 85% not program time). 86general_f_no_memory_left=01009_F_?? ???? ????? 87% The compiler doesn't have enough memory to compile your program. There are 88% several remedies for this: 89% \begin{itemize} 90% \item If you're using the build option of the compiler, try compiling the 91% different units manually. 92% \item If you're compiling a huge program, split it up in units, and compile 93% these separately. 94% \item If the previous two don't work, recompile the compiler with a bigger 95% heap (you can use the \var{-Ch} option for this, \seeo{Ch}) 96% \end{itemize} 97general_i_writingresourcefile=01010_I_???? ?? ???? ????? ???? ????????: $1 98% This message is shown when the compiler writes the Resource String Table 99% file containing all the resource strings for a program. 100general_e_errorwritingresourcefile=01011_E_???? ?? ???? ????? ???? ????????: $1 101% This message is shown when the compiler encountered an error when writing 102% the Resource String Table file 103general_i_fatal=01012_I_????? ??????: 104% Prefix for Fatal Errors 105general_i_error=01013_I_?????: 106% Prefix for Errors 107general_i_warning=01014_I_?????: 108% Prefix for Warnings 109general_i_note=01015_I_????: 110% Prefix for Notes 111general_i_hint=01016_I_???: 112% Prefix for Hints 113general_e_path_does_not_exist=01017_E_????? "$1" ???? ???? 114% The specified path does not exist. 115general_f_compilation_aborted=01018_F_?????? ???? 116% Compilation was aborted. 117general_text_bytes_code=01019_bytes code 118general_text_bytes_data=01020_bytes data 119general_i_number_of_warnings=01021_I_?????? $1 ?????? 120% Total number of warnings issued during compilation. 121general_i_number_of_hints=01022_I_?????? $1 ????? 122% Total number of hints issued during compilation. 123general_i_number_of_notes=01023_I_?????? $1 ????? 124% Total number of notes issued during compilation. 125% \end{description} 126# 127# Scanner 128# 129# 02084 is the last used one 130# 131% \section{Scanner messages.} 132% This section lists the messages that the scanner emits. The scanner takes 133% care of the lexical structure of the pascal file, i.e. it tries to find 134% reserved words, strings, etc. It also takes care of directives and 135% conditional compiling handling. 136% \begin{description} 137scan_f_end_of_file=02000_F_??? ???? ?? ???? 138% this typically happens in one of the following cases : 139% \begin{itemize} 140% \item The source file ends before the final \var{end.} statement. This 141% happens mostly when the \var{begin} and \var{end} statements aren't 142% balanced; 143% \item An include file ends in the middle of a statement. 144% \item A comment was not closed 145% \end{itemize} 146scan_f_string_exceeds_line=02001_F_?????? ????? ????? 147% There is a missing closing ' in a string, so it occupies 148% multiple lines. 149scan_f_illegal_char=02002_F_?? ?? ???? "$1" ($2) 150% An illegal character was encountered in the input file. 151scan_f_syn_expected=02003_F_????? ?????: ???? ? "$1" ??? "$2" ???? 152% This indicates that the compiler expected a different token than 153% the one you typed. It can occur almost everywhere where you make a 154% mistake against the pascal language. 155scan_t_start_include_file=02004_TL_????? ????? ?? ???? ?????? $1 156% When you provide the \var{-vt} switch, the compiler tells you 157% when it starts reading an included file. 158scan_w_comment_level=02005_W_??? ????? $1 ????? 159% When the \var{-vw} switch is used, then the compiler warns you if 160% it finds nested comments. Nested comments are not allowed in Turbo Pascal 161% and can be a possible source of errors. 162scan_n_ignored_switch=02008_N_????? ???? ???? "$1" 163% With \var{-vn} on, the compiler warns if it ignores a switch 164scan_w_illegal_switch=02009_W_??? ???? "$1" ???? ???? 165% You included a compiler switch (i.e. \var{\{\$... \}}) which the compiler 166% does not recognise 167scan_w_switch_is_global=02010_W_????? ???? ???? ???? ?????? 168% The compiler switch is misplaced, and should be located at 169% the start of the unit or program. 170scan_e_illegal_char_const=02011_E_?? ???? ?? ???? 171% This happens when you specify a character with its ASCII code, as in 172% \var{\#96}, but the number is either illegal, or out of range. 173scan_f_cannot_open_input=02012_F_?? ???? ????? ?? ???? "$1" 174% \fpc cannot find the program or unit source file you specified on the 175% command line. 176scan_f_cannot_open_includefile=02013_F_?? ???? ????? ?? ???? ??????? "$1" 177% \fpc cannot find the source file you specified in a \var{\{\$include ..\}} 178% statement. 179scan_e_illegal_pack_records=02015_E_????? ????? ?? ???? ????? "$1" 180% You are specifying the \var{\{\$PACKRECORDS n\} } or \var{\{\$ALIGN n\} } 181% with an illegal value for \var{n}. For \$PACKRECORDS valid alignments are 1, 2, 4, 8, 16, 32, C, 182% NORMAL, DEFAULT, and for \$ALIGN valid alignment are 1, 2, 4, 8, 16, 32, ON, 183% OFF. Under mode MacPas \$ALIGN also supports MAC68K, POWER and RESET. 184scan_e_illegal_pack_enum=02016_E_???? ??????? ?? ????? ?????? "$1" ???? ???? 185% You are specifying the \var{\{\$PACKENUM n\}} with an illegal value for 186% \var{n}. Only 1,2,4, NORMAL or DEFAULT are valid here. 187scan_e_endif_expected=02017_E_???? ?$ENDIF ?????? $1 $2 ?????? ?$3 ???? $4 188% Your conditional compilation statements are unbalanced. 189scan_e_preproc_syntax_error=02018_E_????? ????? ??? ????? ???? ???? 190% There is an error in the expression following the \var{\{\$if ..\}}, $ifc or $setc compiler 191% directives. 192scan_e_error_in_preproc_expr=02019_E_????? ???? ???? 193% There is an error in the expression following the \var{\{\$if ..\}}, $ifc or $setc compiler 194% directives. 195scan_w_macro_cut_after_255_chars=02020_W_???? ????? ????? ????? ?? 255 ????? 196% The contents of macros cannot be longer than 255 characters. 197scan_e_endif_without_if=02021_E_ENDIF ??? IF(N)DEF 198% Your \var{\{\$IFDEF ..\}} and {\{\$ENDIF\}} statements aren't balanced. 199scan_f_user_defined=02022_F_????? ?????: $1 200% A user defined fatal error occurred. see also the \progref 201scan_e_user_defined=02023_E_????? ?????: $1 202% A user defined error occurred. see also the \progref 203scan_w_user_defined=02024_W_????? ?????: $1 204% A user defined warning occurred. see also the \progref 205scan_n_user_defined=02025_N_????? ?????: $1 206% A user defined note was encountered. see also the \progref 207scan_h_user_defined=02026_H_????? ?????: $1 208% A user defined hint was encountered. see also the \progref 209scan_i_user_defined=02027_I_????? ?????: $1 210% User defined information was encountered. see also the \progref 211scan_e_keyword_cant_be_a_macro=02028_E_???? ???? ??????? ???? ????? ???? ????? ????? 212% You cannot redefine keywords with macros. 213scan_f_macro_buffer_overflow=02029_F_????? ???? ???? ??? ????? ?? ????? ?? ???? 214% Your macro or its result was too long for the compiler. 215scan_w_macro_too_deep=02030_W_????? ???? ????? ????? ?? 16. 216% When expanding a macro, macros have been nested to a level of 16. 217% The compiler will expand no further, since this may be a sign that 218% recursion is used. 219scan_w_wrong_styled_switch=02031_W_ ???? ????? ???? ???? ?????? ?????? ???? // 220% Compiler switches should be in normal pascal style comments. 221scan_d_handling_switch=02032_DL_???? ???? "$1" 222% When you set debugging info on (\var{-vd}) the compiler tells you when it 223% is evaluating conditional compile statements. 224scan_c_endif_found=02033_CL_???? ENDIF $1 225% When you turn on conditional messages(\var{-vc}), the compiler tells you 226% where it encounters conditional statements. 227scan_c_ifdef_found=02034_CL_???? IFDEF $1, $2 228% When you turn on conditional messages(\var{-vc}), the compiler tells you 229% where it encounters conditional statements. 230scan_c_ifopt_found=02035_CL_???? IFOPT $1, $2 231% When you turn on conditional messages(\var{-vc}), the compiler tells you 232% where it encounters conditional statements. 233scan_c_if_found=02036_CL_???? IF $1, $2 234% When you turn on conditional messages(\var{-vc}), the compiler tells you 235% where it encounters conditional statements. 236scan_c_ifndef_found=02037_CL_???? IFNDEF $1, $2 237% When you turn on conditional messages(\var{-vc}), the compiler tells you 238% where it encounters conditional statements. 239scan_c_else_found=02038_CL_???? ELSE $1, $2 240% When you turn on conditional messages(\var{-vc}), the compiler tells you 241% where it encounters conditional statements. 242scan_c_skipping_until=02039_CL_????... 243% When you turn on conditional messages(\var{-vc}), the compiler tells you 244% where it encounters conditional statements, and whether it is skipping or 245% compiling parts. 246scan_i_press_enter=02040_I_??? ?? <return> ?????? 247% When the \var{-vi} switch is used, the compiler stops compilation 248% and waits for the \var{Enter} key to be pressed when it encounters 249% a \var{\{\$STOP\}} directive. 250scan_w_unsupported_switch=02041_W_??? "$1" ???? ???? 251% When warnings are turned on (\var{-vw}) the compiler warns you about 252% unsupported switches. This means that the switch is used in Delphi or 253% Turbo Pascal, but not in \fpc 254scan_w_illegal_directive=02042_W_????? ????? "$1" ???? ????? 255% When warings are turned on (\var{-vw}) the compiler warns you about 256% unrecognised switches. For a list of recognised switches, \progref 257scan_t_back_in=02043_TL_???? ?$1 258% When you use (\var{-vt}) the compiler tells you when it has finished 259% reading an include file. 260scan_w_unsupported_app_type=02044_W_??? ????? ???? ?????????: "$1" 261% You get this warning, if you specify an unknown application type 262% with the directive \var{\{\$APPTYPE\}} 263scan_w_app_type_not_support=02045_W_APPTYPE ???? ???? ?"? ??????? ????? ??????? 264% The \var{\{\$APPTYPE\}} directive is supported by certain operating systems only. 265scan_w_description_not_support=02046_W_DESCRIPTION ???? ???? ?"? ????? ?????? ??????? 266% The \var{\{\$DESCRIPTION\}} directive is not supported on this target OS 267scan_n_version_not_support=02047_N_VERSION ???? ???? ?"? ????? ????? ??????? 268% The \var{\{\$VERSION\}} directive is not supported on this target OS 269scan_n_only_exe_version=02048_N_VERSION ?? ????? exe ?? DLL 270% The \var{\{\$VERSION\}} directive is only used for executable or DLL sources. 271scan_w_wrong_version_ignored=02049_W_????? ???? ?????? VERSION: "$1" 272% The \var{\{\$VERSION\}} directive format is majorversion.minorversion 273% where majorversion and minorversion are words. 274scan_e_illegal_asmmode_specifier=02050_E_????? ??????? ?????? "$1" ???? ???? 275% When you specify an assembler mode with the \var{\{\$ASMMODE xxx\}} 276% the compiler didn't recognize the mode you specified. 277scan_w_no_asm_reader_switch_inside_asm=02051_W_??? ???? ?ASM ???? ????? ???? ???? ??????. "$1" ???? ????? ?? ?????? ????/ 278% It is not possible to switch from one assembler reader to another 279% inside an assembler block. The new reader will be used for next 280% assembler statements only. 281scan_e_wrong_switch_toggle=02052_E_????? ???? ????. ????? ?ON/OFF ?? ? +/- 282% You need to use ON or OFF or a + or - to toggle the switch 283scan_e_resourcefiles_not_supported=02053_E_???? ??????? ???? ???? ???? ????? 284% The target you are compiling for doesn't support resource files. 285scan_w_include_env_not_found=02054_W_????? ?????? "$1" ?? ???? ?????? 286% The included environment variable can't be found in the environment, it will 287% be replaced by an empty string instead. 288scan_e_invalid_maxfpureg_value=02055_E_??? ?? ???? ??????? ???? ?FPC 289% Valid values for this directive are 0..8 and NORMAL/DEFAULT 290scan_w_only_one_resourcefile_supported=02056_W_?? ???? ?????? ??? ???? ???? ?? 291% The target you are compiling for supports only one resource file. 292% The first resource file found is used, the others are discarded. 293scan_w_macro_support_turned_off=02057_W_?????? ????? ???? 294% A macro declaration has been found, but macro support is currently off, 295% so the declaration will be ignored. To turn macro support on compile with 296% -Sm on the commandline or add \{\$MACRO ON\} in the source 297scan_e_invalid_interface_type=02058_E_????? ??? ???? ?? ????. ?????? ?????? ?? COM, CORBA ?? DEFAULT 298% The interface type that was specified is not supported 299scan_w_appid_not_support=02059_W_APPID ???? ?? ?PALMOS 300% The \var{\{\$APPID\}} directive is only supported for the PalmOS target. 301scan_w_appname_not_support=02060_W_APPNAME ???? ?? ?PALMOS 302% The \var{\{\$APPNAME\}} directive is only supported for the PalmOS target. 303scan_e_string_exceeds_255_chars=02061_E_?????? ????? ?? ????? ????? ??? 255 ????? 304% A single string constant can contain at most 255 chars. Try splitting up the 305% string in multiple smaller parts and concatenate them with a + operator. 306scan_f_include_deep_ten=02062_F_????? ???? ?include ??? ????? ?16 307% When including include files the files have been nested to a level of 16. 308% The compiler will expand no further, since this may be a sign that 309% recursion is used. 310scan_e_too_many_push=02063_F_???? ???? ????? PUSH 311% A maximum of 20 levels is allowed. This error occurs only in mode MacPas. 312scan_e_too_many_pop=02064_E_POP ??? ????? ?? PUSH 313% This error occurs only in mode MacPas. 314scan_e_error_macro_lacks_value=02065_E_???? "$1" ?? ???? ????? 315% Thus the conditional compile time expression cannot be evaluated. 316scan_e_wrong_switch_toggle_default=02066_E_????? ???? ????, ????? ? ON/OFF/DEFAULT ?? ?+/-/* 317% You need to use ON or OFF or DEFAULT or a + or - or * to toggle the switch 318scan_e_mode_switch_not_allowed=02067_E_??? ??? "$1" ?? ????? 319% A mode switch has already been encountered, or, in case of option -Mmacpas, 320% a mode switch occur after UNIT. 321scan_e_error_macro_undefined=02068_E_????? ??? ????? "$1" ?? ?????. 322% Thus the conditional compile time expression cannot be evaluated. Only in mode MacPas. 323scan_e_utf8_bigger_than_65535=02069_E_???? ??? UTF-8 ????? ???? ?65535 324% \fpc handles utf-8 strings internally as widestrings e.g. the char codes are limited to 65535 325scan_e_utf8_malformed=02070_E_?????? UTF-8 ????? 326% The given string isn't a valid UTF-8 string 327scan_c_switching_to_utf8=02071_C_UTF-8 signature found, using UTF-8 encoding 328% The compiler found an UTF-8 encoding signature (\$ef, \$bb, \$bf) at the beginning of a file, 329% so it interprets it as an UTF-8 file 330scan_e_compile_time_typeerror=02072_E_????? ???? ?????: ???? $1 ??? ????? $2 ?$3 331% Type check of a compile time expression failed. 332scan_n_app_type_not_support=02073_N_APPTYPE ?? ???? ?????? ?????? ??????? 333% The \var{\{\$APPTYPE\}} directive is supported by certain operating systems only. 334scan_e_illegal_optimization_specifier=02074_E_???? ????? ?? ???? "$1" 335% When you specify an optimization with the \var{\{\$OPTIMIZATION xxx\}} 336% the compiler didn't recognize the optimization you specified. 337scan_w_setpeflags_not_support=02075_W_SETPEFLAGS ???? ???? ?????? ?????? ??????? 338% The \var{\{\$SETPEFLAGS\}} directive is not supported by the target OS 339scan_w_imagebase_not_support=02076_W_IMAGEBASE ???? ???? ?? ??? ????? ?????? ??????? 340% The \var{\{\$IMAGEBASE\}} directive is not supported by the target OS 341scan_w_minstacksize_not_support=02077_W_MINSTACKSIZE ???? ???? ?? ??? ????? ?????? ??????? 342% The \var{\{\$MINSTACKSIZE\}} directive is not supported by the target OS 343scan_w_maxstacksize_not_support=02078_W_MAXSTACKSIZE ???? ???? ?? ??? ????? ?????? ??????? 344% The \var{\{\$MAXSTACKSIZE\}} directive is not supported by the target OS 345scanner_e_illegal_warn_state=02079_E_????? ?? ???? ?????? $WARN 346% Only ON and OFF can be used as state with a \$warn compiler directive 347scan_e_only_packset=02080_E_??? ?? ????? ?? ???? 348% Only 0, 1, 2, 4, 8, DEFAULT and NORMAL are allowed as packset parameter 349scan_w_pic_ignored=02081_W_????? ?????? PIC 350% Several targets like windows do not support neither need PIC so the PIC directive and switch are 351% ignored. 352scan_w_unsupported_switch_by_target=02082_W_???? "$1" ???? ???? ???? ????? ????? 353% Some compiler switches like \$E are not supported by all targets. 354scan_w_frameworks_darwin_only=02084_W_???????? ??????? ????? ?????? ?? ???? Darwin/Mac OS X 355% Frameworks are not a known concept, or at least not supported by FPC, on operating systems other than Darwin/Mac OS X. 356scan_e_illegal_minfpconstprec=02085_E_???? ???? ????? ?? ?????? ???????? ????????? "$1" ???? ???? 357% Valid minimal precisions for floating point constants are default, 32 and 64, which mean respectively minimal (usually 32 bit), 32 bit and 64 bit precision. 358% \end{description} 359# 360# Parser 361# 362# 03192 is the last used one 363# 364% \section{Parser messages} 365% This section lists all parser messages. The parser takes care of the 366% semantics of you language, i.e. it determines if your pascal constructs 367% are correct. 368% \begin{description} 369parser_e_syntax_error=03000_E_???? - ????? ??????? 370% An error against the Turbo Pascal language was encountered. This happens 371% typically when an illegal character is found in the sources file. 372parser_e_dont_nest_interrupt=03004_E_???????? ????? ???? ????? ????? ?????? 373% An \var{INTERRUPT} procedure must be global. 374parser_w_proc_directive_ignored=03005_W_????? ???? ???????? "$1" 375% The specified procedure directive is ignored by FPC programs. 376parser_e_no_overload_for_all_procs=03006_E_?? ?? ??????? ?? "$1" ????? ????? OVERLOAD 377% When you want to use overloading using the \var{OVERLOAD} directive, then 378% all declarations need to have \var{OVERLOAD} specified. 379parser_e_export_name_double=03008_E_???????? ?????? ?? ???????? "$1" 380% Exported function names inside a specific DLL must all be different 381parser_e_export_ordinal_double=03009_E_???????? ?????? ?????? ???????? "$1" 382% Exported function names inside a specific DLL must all be different 383parser_e_export_invalid_index=03010_E_?????? ?? ???? ?????? ???????? 384% DLL function index must be in the range \var{1..\$FFFF} 385parser_w_parser_reloc_no_debug=03011_W_????? ????? ????? ?????? ?? ?????? ????? DLL ?? ???? ????. ?????. 386parser_w_parser_win32_debug_needs_WN=03012_W_????? ????? ?????? ?win32 ?? ???? ?? ????? ?????? ?"? ??????? -WN 387% Stabs info is wrong for relocatable DLL or EXES use -WN 388% if you want to debug win32 executables. 389parser_e_constructorname_must_be_init=03013_E_?? ???? ???? ????? INIT 390% You are declaring an object constructor with a name which is not \var{init}, and the 391% \var{-Ss} switch is in effect. See the \var{-Ss} switch (\seeo{Ss}). 392parser_e_destructorname_must_be_done=03014_E_?? ???? ???? ????? DONE 393% You are declaring an object destructor with a name which is not \var{done}, and the 394% \var{-Ss} switch is in effect. See the \var{-Ss} switch (\seeo{Ss}). 395parser_e_proc_inline_not_supported=03016_E_???????? INLINE ?? ????? 396% You tried to compile a program with C++ style inlining, and forgot to 397% specify the \var{-Si} option (\seeo{Si}). The compiler doesn't support C++ 398% styled inlining by default. 399parser_w_constructor_should_be_public=03018_W_???? ???? ????? ?????? 400% Constructors must be in the 'public' part of an object (class) declaration. 401parser_w_destructor_should_be_public=03019_W_???? ???? ????? ?????? 402% Destructors must be in the 'public' part of an object (class) declaration. 403parser_n_only_one_destructor=03020_N_????? ????? ???? ??? ???? 404% You can declare only one destructor for a class. 405parser_e_no_local_objects=03021_E_?????? ????? ??????? ???? ?????? 406% Classes must be defined globally. They cannot be defined inside a 407% procedure or function 408parser_f_no_anonym_objects=03022_F_?????? ????? ????????? ???? ?????? 409% An invalid object (class) declaration was encountered, i.e. an 410% object or class without methods that isn't derived from another object or 411% class. For example: 412% \begin{verbatim} 413% Type o = object 414% a : longint; 415% end; 416% \end{verbatim} 417% will trigger this error. 418parser_n_object_has_no_vmt=03023_N_???????? "$1" ??? VMT 419% This is a note indicating that the declared object has no 420% virtual method table. 421parser_e_illegal_parameter_list=03024_E_????? ??????? ?? ????? 422% You are calling a function with parameters that are of a different type than 423% the declared parameters of the function. 424parser_e_wrong_parameter_size=03026_E_???? ???? ?? ??????? ???? ???? ?????? ? "$1" 425% There is an error in the parameter list of the function or procedure, 426% the number of parameters is not correct. 427parser_e_overloaded_no_procedure=03027_E_???? ?????? ????? "$1" ???? ??????? 428% The compiler encountered a symbol with the same name as an overloaded 429% function, but it is not a function it can overload. 430parser_e_overloaded_have_same_parameters=03028_E_???????? ?????? ????? ?????? ?? ???? ????? ??????? 431% You're declaring overloaded functions, but with the same parameter list. 432% Overloaded function must have at least 1 different parameter in their 433% declaration. 434parser_e_header_dont_match_forward=03029_E_????? ???????? ???? ????? ?? ?????? ?????? "$1" 435% You declared a function with same parameters but 436% different result type or function modifiers. 437parser_e_header_different_var_names=03030_E_????? ???????? "$1" ???? ????? ?? ??????: ?? ????? ????? $2 => $3 438% You declared the function in the \var{interface} part, or with the 439% \var{forward} directive, but define it with a different parameter list. 440parser_n_duplicate_enum=03031_N_????? ???? ???? ?????? ????? ???? ???? 441% \fpc allows enumeration constructions as in C. Given the following 442% declaration two declarations: 443% \begin{verbatim} 444% type a = (A_A,A_B,A_E:=6,A_UAS:=200); 445% type a = (A_A,A_B,A_E:=6,A_UAS:=4); 446% \end{verbatim} 447% The second declaration would produce an error. \var{A\_UAS} needs to have a 448% value higher than \var{A\_E}, i.e. at least 7. 449parser_e_no_with_for_variable_in_other_segments=03033_E_With ???? ????? ?????? ??????? ????? ???? 450% With stores a variable locally on the stack, 451% but this is not possible if the variable belongs to another segment. 452parser_e_too_much_lexlevel=03034_E_??????? ?????? > 31 453% You can nest function definitions only 31 times. 454parser_e_range_check_error=03035_E_????? ?????? ???? ??? ????? ?????? 455% The constants are out of their allowed range. 456parser_w_range_check_error=03036_W_????? ?????? ???? ??? ????? ?????? 457% The constants are out of their allowed range. 458parser_e_double_caselabel=03037_E_????? ????? ????? ?case 459% You are specifying the same label 2 times in a \var{case} statement. 460parser_e_case_lower_less_than_upper_bound=03038_E_????? ????? ??? ?????? ??????? 461% The upper bound of a \var{case} label is less than the lower bound and this 462% is useless 463parser_e_type_const_not_possible=03039_E_????? ????? ?????? ?? ?????? ?? ?????? ????? 464% You cannot declare a constant of type class or object. 465parser_e_no_overloaded_procvars=03040_E_?????? ?? ???????? ?????? ????? ???? ?????? 466% You are trying to assign an overloaded function to a procedural variable. 467% This is not allowed 468parser_e_invalid_string_size=03041_E_???? ?????? ???? ????? ?? ????? ?1 ?255 469% The length of a shortstring in Pascal is limited to 255 characters. You are 470% trying to declare a string with length lower than 1 or greater than 255 471parser_w_use_extended_syntax_for_objects=03042_W_????? ?????? ????? ?? NEW ?DISPOSE ??????? ?? ??????? 472% If you have a pointer \var{a} to a class type, then the statement 473% \var{new(a)} will not initialize the class (i.e. the constructor isn't 474% called), although space will be allocated. you should issue the 475% \var{new(a,init)} statement. This will allocate space, and call the 476% constructor of the object 477parser_w_no_new_dispose_on_void_pointers=03043_W_?????? ?????? ?? ????? ?? NEW ? DISPOSE ??? ?????? 478parser_e_no_new_dispose_on_void_pointers=03044_E_???? ????? ?????? ?????? ?? ????? ?? NEW ?? DISPOSE 479% You cannot use \var{new(p)} or \var{dispose(p)} if \var{p} is an untyped pointer 480% because no size is associated to an untyped pointer. 481% Accepted for compatibility in \var{tp} and \var{delphi} modes. 482parser_e_class_id_expected=03045_E_???? ????? ????? 483% This happens when the compiler scans a procedure declaration that contains 484% a dot, 485% i.e., a object or class method, but the type in front of the dot is not 486% a known type. 487parser_e_no_type_not_allowed_here=03046_E_??? ???? ?? ????? ?????? ?????? 488% You cannot use a type inside an expression. 489parser_e_methode_id_expected=03047_E_???? ????? ????? 490% This identifier is not a method. 491% This happens when the compiler scans a procedure declaration that contains 492% a dot, i.e., a object or class method, but the procedure name is not a 493% procedure of this type. 494parser_e_header_dont_match_any_member=03048_E_????? ???????? ?? ??? ??????? ?? ?????? "$1" 495% This identifier is not a method. 496% This happens when the compiler scans a procedure declaration that contains 497% a dot, i.e., a object or class method, but the procedure name is not a 498% procedure of this type. 499parser_d_procedure_start=03049_DL_????????/??????? $1 500% When using the \var{-vd} switch, the compiler tells you when it starts 501% processing a procedure or function implementation. 502parser_e_error_in_real=03050_E_???? ?? ???? ???? ???? ???? 503% The compiler expects a floating point expression, and gets something else. 504parser_e_fail_only_in_constructor=03051_E_FAIL ???? ????? ?????? ?? ???? ???? 505% You are using the \var{fail} keyword outside a constructor method. 506parser_e_no_paras_for_destructor=03052_E_?????? ?? ?????? ????? ??????? 507% You are declaring a destructor with a parameter list. Destructor methods 508% cannot have parameters. 509parser_e_only_class_methods_via_class_ref=03053_E_?? ?????? ????? ?????? ????? ??????? ????????? ????? 510% This error occurs in a situation like the following: 511% \begin{verbatim} 512% Type : 513% Tclass = Class of Tobject; 514% 515% Var C : TClass; 516% 517% begin 518% ... 519% C.free 520% \end{verbatim} 521% \var{Free} is not a class method and hence cannot be called with a class 522% reference. 523parser_e_only_class_methods=03054_E_?? ????? ????? ????? ???? ?????? ????? 524% This is related to the previous error. You cannot call a method of an object 525% from a inside a class method. The following code would produce this error: 526% \begin{verbatim} 527% class procedure tobject.x; 528% 529% begin 530% free 531% \end{verbatim} 532% Because free is a normal method of a class it cannot be called from a class 533% method. 534parser_e_case_mismatch=03055_E_?????? ???? CASE ???? ??????? 535% One of the labels is not of the same type as the case variable. 536parser_e_illegal_symbol_exported=03056_E_?? ???? ????? ?? ???? ??????? 537% You can only export procedures and functions when you write a library. You 538% cannot export variables or constants. 539parser_w_should_use_override=03057_W_????? ????? ????? ?"? "$1" 540% A method that is declared \var{virtual} in a parent class, should be 541% overridden in the descendent class with the \var{override} directive. If you 542% don't specify the \var{override} directive, you will hide the parent method; 543% you will not override it. 544parser_e_nothing_to_be_overridden=03058_E_??? ????? ?????? ?? ??? ??? ???? ?????: "$1" 545% You are trying to \var{override} a virtual method of a parent class that does 546% not exist. 547parser_e_no_procedure_to_access_property=03059_E_?? ???? ???? ???? ??????? 548% You specified no \var{read} directive for a property. 549parser_w_stored_not_implemented=03060_W_?????? ???? ???? ????? ????? 550% The \var{stored} directive is not yet implemented 551parser_e_ill_property_access_sym=03061_E_???? ?? ???? ????? ??????? 552% There is an error in the \var{read} or \var{write} directives for an array 553% property. When you declare an array property, you can only access it with 554% procedures and functions. The following code would cause such an error. 555% \begin{verbatim} 556% tmyobject = class 557% i : integer; 558% property x [i : integer]: integer read I write i; 559% \end{verbatim} 560% 561parser_e_cant_access_protected_member=03062_E_?? ???? ???? ???? ???? ???????? ?????? 562% Fields that are declared in a \var{protected} section of an object or class 563% declaration cannot be accessed outside the module where the object is 564% defined, or outside descendent object methods. 565parser_e_cant_access_private_member=03063_E_?? ???? ???? ???? ???? ???????? ?????? 566% Fields that are declared in a \var{private} section of an object or class 567% declaration cannot be accessed outside the module where the class is 568% defined. 569parser_e_overridden_methods_not_same_ret=03066_E_????? ????? ????? ????? ????? ??? ???? ??????: "$2" ?????? ?"? "$1", ??? ????? ??? ????? ??? 570% If you declare overridden methods in a class definition, they must 571% have the same return type. 572parser_e_dont_nest_export=03067_E_?????? ???????? EXPORT ?? ?????? ????? ??????? 573% You cannot declare a function or procedure within a function or procedure 574% that was declared as an export procedure. 575parser_e_methods_dont_be_export=03068_E_?? ???? ????? ?? ?????? 576% You cannot declare a procedure that is a method for an object as 577% \var{export}ed. 578parser_e_call_by_ref_without_typeconv=03069_E_?????? ?????? ?? ????? ???? ????? ???: ???? "$1" ???? ?"$2" 579% When calling a function declared with \var{var} parameters, the variables in 580% the function call must be of exactly the same type. There is no automatic 581% type conversion. 582parser_e_no_super_class=03070_E_?????? ????? ????? ?? ?? ?????? ??????? 583% When calling inherited methods, you are trying to call a method of a non-related 584% class. You can only call an inherited method of a parent class. 585parser_e_self_not_in_method=03071_E_SELF ????? ?? ??????? 586% You are trying to use the \var{self} parameter outside an object's method. 587% Only methods get passed the \var{self} parameters. 588parser_e_generic_methods_only_in_methods=03072_E_?????? ?????? ?????? ?????? ?? ???? ?????? ????? ?? ??? ???? ???????? 589% A construction like \var{sometype.somemethod} is only allowed in a method. 590parser_e_illegal_colon_qualifier=03073_E_????? ?? ???? ?? ':' 591% You are using the format \var{:} (colon) 2 times on an expression that 592% is not a real expression. 593parser_e_illegal_set_expr=03074_E_????? ?????? ???? ????? ?????? ?? ????? ???? 594% The declaration of a set contains an error. Either one of the elements is 595% outside the range of the set type, either two of the elements are in fact 596% the same. 597parser_e_pointer_to_class_expected=03075_E_???? ?????? ??????? 598% You specified an illegal type in a \var{new} statement. 599% The extended syntax of \var{new} needs an object as a parameter. 600parser_e_expr_have_to_be_constructor_call=03076_E_?????? ???? ????? ????? ???? 601% When using the extended syntax of \var{new}, you must specify the constructor 602% method of the object you are trying to create. The procedure you specified 603% is not a constructor. 604parser_e_expr_have_to_be_destructor_call=03077_E_?????? ???? ????? ????? ???? 605% When using the extended syntax of \var{dispose}, you must specify the 606% destructor method of the object you are trying to dispose of. 607% The procedure you specified is not a destructor. 608parser_e_invalid_record_const=03078_E_??? ?? ???? ?? ??????? ?????? 609% When declaring a constant record, you specified the fields in the wrong 610% order. 611parser_e_false_with_expr=03079_E_??? ????? ???? ????? ????? ????? ?? ????? 612% A \var{with} statement needs an argument that is of the type \var{record} 613% or \var{class}. You are using \var{with} on an expression that is not of 614% this type. 615parser_e_void_function=03080_E_???????? ?? ????? ?????? ??? 616% In \fpc, you can specify a return value for a function when using 617% the \var{exit} statement. This error occurs when you try to do this with a 618% procedure. Procedures cannot return a value. 619parser_e_only_methods_allowed=03081_E_??????? ???????? ?????? ????? ??????? 620% You're declaring a procedure as destructor, constructor or class operator, when the 621% procedure isn't a class method. 622parser_e_operator_not_overloaded=03082_E_????????? ?? ????? ????? 623% You're trying to use an overloaded operator when it is not overloaded for 624% this type. 625parser_e_no_such_assignment=03083_E_?? ???? ????? ????? ?????? ????? ????? 626% You can not overload assignment for types 627% that the compiler considers as equal. 628parser_e_overload_impossible=03084_E_???? ????? ?????? ???????? ????? ????? 629% The combination of operator, arguments and return type are 630% incompatible. 631parser_e_no_reraise_possible=03085_E_?? ???? ????? ????? 632% You are trying to raise an exception where it is not allowed. You can only 633% raise exceptions in an \var{except} block. 634parser_e_no_new_or_dispose_for_classes=03086_E_?????? ?????? ?? NEW ?? DISPOSE ?? ????? ??????? 635% You cannot generate an instance of a class with the extended syntax of 636% \var{new}. The constructor must be used for that. For the same reason, you 637% cannot call \var{dispose} to de-allocate an instance of a class, the 638% destructor must be used for that. 639parser_e_procedure_overloading_is_off=03088_E_??????? ?????????? ?????? ????? ???? 640% When using the \var{-So} switch, procedure overloading is switched off. 641% Turbo Pascal does not support function overloading. 642parser_e_overload_operator_failed=03089_E_?? ???? ?????? ?? ??? ???????? ??????. ????? ?????????? ??????? ?????? (?? ????) ??: $1 643% You are trying to overload an operator which cannot be overloaded. 644% The following operators can be overloaded : 645% \begin{verbatim} 646% +, -, *, /, =, >, <, <=, >=, is, as, in, **, := 647% \end{verbatim} 648parser_e_comparative_operator_return_boolean=03090_E_??????? ??????? ???? ?????? ??? ??????? 649% When overloading the \var{=} operator, the function must return a boolean 650% value. 651parser_e_only_virtual_methods_abstract=03091_E_?? ???? ?????????? ????? ????? ????? 652% You are declaring a method as abstract, when it is not declared to be 653% virtual. 654parser_f_unsupported_feature=03092_F_????? ??????? ?? ?????! 655% You're trying to force the compiler into doing something it cannot do yet. 656parser_e_mix_of_classes_and_objects=03093_E_?????? ?? ????? ????? (??????, ???, ???? ???') ???? ????? 657% You cannot derive \var{objects}, \var{classes}, \var{cppclasses} and \var{interfaces} interttwined . E.g. 658% a class cannot have an object as parent and vice versa. 659parser_w_unknown_proc_directive_ignored=03094_W_????? ?????? ?????: "$1" 660% The procedure directive you specified is unknown. 661parser_e_absolute_only_one_var=03095_E_absolute ???? ?????? ?? ?? ????? ??? 662% You cannot specify more than one variable before the \var{absolute} directive. 663% Thus, the following construct will provide this error: 664% \begin{verbatim} 665% Var Z : Longint; 666% X,Y : Longint absolute Z; 667% \end{verbatim} 668% \item [ absolute can only be associated a var or const ] 669% The address of a \var{absolute} directive can only point to a variable or a 670% typed constant. Therefore, the following code will produce this error: 671% \begin{verbatim} 672% Procedure X; 673% 674% var p : longint absolute x; 675% \end{verbatim} 676% 677parser_e_absolute_only_to_var_or_const=03096_E_???? ?????? ?absolute ?? ?? ????? ?? ???? 678% The address of a \var{absolute} directive can only point to a variable or 679% constant. Therefore, the following code will produce this error: 680% \begin{verbatim} 681% Procedure X; 682% 683% var p : longint absolute x; 684% \end{verbatim} 685% 686parser_e_initialized_only_one_var=03097_E_???? ????? ?? ????? ??? 687% You cannot specify more than one variable with a initial value 688% in Delphi mode. 689parser_e_abstract_no_definition=03098_E_????? ?????? ???? ????? ?????? (?? ??? ?? ???????) 690% Abstract methods can only be declared, you cannot implement them. They 691% should be overridden by a descendant class. 692parser_e_overloaded_must_be_all_global=03099_E_????? ???? ?? ???????? ???? ????? ????? ?????? (????? ????? ??????) 693% You are defining a overloaded function in the implementation part of a unit, 694% but there is no corresponding declaration in the interface part of the unit. 695parser_w_virtual_without_constructor=03100_W_????? ??????? ??????????? ??? ???? ? "$1" 696% If you declare objects or classes that contain virtual methods, you need 697% to have a constructor and destructor to initialize them. The compiler 698% encountered an object or class with virtual methods that doesn't have 699% a constructor/destructor pair. 700parser_c_macro_defined=03101_CL_????? ?????: $1 701% When \var{-vc} is used, the compiler tells you when it defines macros. 702parser_c_macro_undefined=03102_CL_????? ?? ?????: $1 703% When \var{-vc} is used, the compiler tells you when it undefines macros. 704parser_c_macro_set_to=03103_CL_????? $1 ????? ? $2 705% When \var{-vc} is used, the compiler tells you what values macros get. 706parser_i_compiling=03104_I_???? $1 707% When you turn on information messages (\var{-vi}), the compiler tells you 708% what units it is recompiling. 709parser_u_parsing_interface=03105_UL_???? ?? ????? ?? ?????? $1 710% This tells you that the reading of the interface 711% of the current unit starts 712parser_u_parsing_implementation=03106_UL_???? ?? ?????? ?? $1 713% This tells you that the code reading of the implementation 714% of the current unit, library or program starts 715parser_d_compiling_second_time=03107_DL_???? ?? $1 ???? ?????? 716% When you request debug messages (\var{-vd}) the compiler tells you what 717% units it recompiles for the second time. 718parser_e_no_property_found_to_override=03109_E_?? ????? ????? ?????? 719% You want to override a property of a parent class, when there is, in fact, 720% no such property in the parent class. 721parser_e_only_one_default_property=03110_E_?? ????? ??? ?? ????? ???? ????? 722% You specified a property as \var{Default}, but the class already has a 723% default property, and a class can have only one default property. 724parser_e_property_need_paras=03111_E_????? ?? ????? ???? ????? ????? ????? ?? ???? 725% Only array properties of classes can be made \var{default} properties. 726parser_e_constructor_cannot_be_not_virtual=03112_E_?????? ?????????? ?????? ?? ?????? 727% You cannot have virtual constructors in objects. You can only have them 728% in classes. 729parser_e_no_default_property_available=03113_E_??? ????? ???? ???? ???? ?????? 730% You are trying to access a default property of a class, but this class (or one of 731% its ancestors) doesn't have a default property. 732parser_e_cant_have_published=03114_E_?????? ???? ????? ????? ?? ??? published, ????? ???? {$M+} 733% If you want a \var{published} section in a class definition, you must 734% use the \var{\{\$M+\}} switch, whch turns on generation of type 735% information. 736parser_e_forward_declaration_must_be_resolved=03115_E_????? ????? ??????? ?? ?????? "$1" ???? ?????? ?? ?????? ????? 737% To be able to use an object as an ancestor object, it must be defined 738% first. This error occurs in the following situation: 739% \begin{verbatim} 740% Type ParentClas = Class; 741% ChildClass = Class(ParentClass) 742% ... 743% end; 744% \end{verbatim} 745% Where \var{ParentClass} is declared but not defined. 746parser_e_no_local_operator=03116_E_?????? ????????? ????? ???? ???? 747% You cannot overload locally, i.e. inside procedures or function 748% definitions. 749parser_e_proc_dir_not_allowed_in_interface=03117_E_???? ????? "$1" ???? ????? ?????? ???? ????? 750% This procedure directive is not allowed in the \var{interface} section of 751% a unit. You can only use it in the \var{implementation} section. 752parser_e_proc_dir_not_allowed_in_implementation=03118_E_???? ????? "$1" ???? ????? ???? ??????? 753% This procedure directive is not defined in the \var{implementation} section of 754% a unit. You can only use it in the \var{interface} section. 755parser_e_proc_dir_not_allowed_in_procvar=03119_E_???? ????? "$1" ???? ????? ???? ?????? ?????? 756% This procedure directive cannot be part of a procedural or function 757% type declaration. 758parser_e_function_already_declared_public_forward=03120_E_????? ???????? "$1" ??? ????? 759% You will get this error if a function is defined as \var{forward} twice. 760% Or it is once in the \var{interface} section, and once as a \var{forward} 761% declaration in the \var{implmentation} section. 762parser_e_not_external_and_export=03121_E_?? ???? ?????? ?? ? EXPORT ??? EXTERNAL 763% These two procedure directives are mutually exclusive 764parser_h_not_supported_for_inline=03123_H_"$1" ???? ???? ????? ???? ???????/???? inline 765% Inline procedures don't support this declaration. 766parser_h_inlining_disabled=03124_H_?????? ????? ????? 767% Inlining of procedures is disabled. 768parser_i_writing_browser_log=03125_I_???? ???? ????? $1 769% When information messages are on, the compiler warns you when it 770% writes the browser log (generated with the \var{\{\$Y+ \}} switch). 771parser_h_maybe_deref_caret_missing=03126_H_????? ?? ??? ???? ?????? 772% The compiler thinks that a pointer may need a dereference. 773parser_f_assembler_reader_not_supported=03127_F_??? ????? ????? ????? 774% The selected assembler reader (with \var{\{\$ASMMODE xxx\}} is not 775% supported. The compiler can be compiled with or without support for a 776% particular assembler reader. 777parser_e_proc_dir_conflict=03128_E_???? ?????? "$1" ????? ?? ?????? ????? 778% You specified a procedure directive that conflicts with other directives. 779% for instance \var{cdecl} and \var{pascal} are mutually exclusive. 780parser_e_call_convention_dont_match_forward=03129_E_?????? ?????? ??????? ???? ??? ?????? ???????? 781% This error happens when you declare a function or procedure with 782% e.g. \var{cdecl;} but omit this directive in the implementation, or vice 783% versa. The calling convention is part of the function declaration, and 784% must be repeated in the function definition. 785parser_e_property_cant_have_a_default_value=03131_E_?????? ???? ?????? ????? ??? ????? ???? 786% Set properties or indexed properties cannot have a default value. 787parser_e_property_default_value_must_const=03132_E_??? ????? ?????? ?? ?????? ???? ????? ???? 788% The value of a \var{default} declared property must be known at compile 789% time. The value you specified is only known at run time. This happens 790% .e.g. if you specify a variable name as a default value. 791parser_e_cant_publish_that=03133_E_???? ???? ???? ????? ?????? ???? ????? ??? ?????? ???? ?????? 792% Only class type variables can be in a \var{published} section of a class 793% if they are not declared as a property. 794parser_e_cant_publish_that_property=03134_E_??? ?? ?? ????? ???? ???? ????? ?????? 795% Properties in a \var{published} section cannot be array properties. 796% they must be moved to public sections. Properties in a \var{published} 797% section must be an ordinal type, a real type, strings or sets. 798parser_e_empty_import_name=03136_E_???? ?? ????? 799% Some targets need a name for the imported procedure or a \var{cdecl} specifier 800parser_e_division_by_zero=03138_E_???? ???? 801% There is a division by zero encounted 802parser_e_invalid_float_operation=03139_E_????? ??????? ?? ????? 803% An operation on two real type values produced an overflow or a division 804% by zero. 805parser_e_array_lower_less_than_upper_bound=03140_E_????? ?????? ???? ???? ?????? ?????? 806% The upper bound of a an array declaration is less than the lower bound and this 807% is not possible 808parser_w_string_too_long=03141_W_???? ??????? ?? "$1" ???? ???? ? "$1" 809% The size of the constant string is larger than the size you specified in 810% string type definition 811parser_e_string_larger_array=03142_E_???? ??????? ???? ???? ????? ???? ?????? 812% The size of the constant string is larger than the size you specified in 813% the array[x..y] of char definition 814parser_e_ill_msg_expr=03143_E_????? ?? ?????? ???? ?????? ???? ???? 815% \fpc supports only integer or string values as message constants 816parser_e_ill_msg_param=03144_E_????? ??????? ???? ????? ????? ???? ?? ??????? 817% A method declared with the \var{message}-directive as message handler 818% can take only one parameter which must be declared as call by reference 819% Parameters are declared as call by reference using the \var{var}-directive 820parser_e_duplicate_message_label=03145_E_????? ????? ?????: "$1" 821% A label for a message is used twice in one object/class 822parser_e_self_in_non_message_handler=03146_E_Self ???? ????? ????? ?????? ?? ???? ??????? 823% The self parameter can only be passed explicitly to a method which 824% is declared as message handler. 825parser_e_threadvars_only_sg=03147_E_Threadvars ?????? ????? ?????? ?? ???????? 826% Threadvars must be static or global, you can't declare a thread 827% local to a procedure. Local variables are always local to a thread, 828% because every thread has its own stack and local variables 829% are stored on the stack 830parser_f_direct_assembler_not_allowed=03148_F_?????? ????? ?????? ???? ???? ???? ?????? ???????? 831% You can't use direct assembler when using a binary writer, choose an 832% other outputformat or use another assembler reader 833parser_w_no_objpas_use_mode=03149_W_???? ????? ?????? OBJPAS ??????, ?? ?????? ? \{\$mode objfpc\} ?? ? \{\$mode delphi\} ????? 834% You are trying to load the ObjPas unit manually from a uses clause. This is 835% not a good idea. Use the \var{\{\$mode objfpc\}} or 836% \var{\{\$mode delphi\}} 837% directives which load the unit automatically 838parser_e_no_object_override=03150_E_OVERRIDE ???? ???? ????? ?????? ?????????? 839% Override is not supported for objects, use \var{virtual} instead to override 840% a method of a parent object 841parser_e_cant_use_inittable_here=03151_E_?????? ?????? ??? ?????? ????? ?? ????? ???? ?????? ????? ??????? variant 842% Some data type (e.g. \var{ansistring}) needs initialization/finalization 843% code which is implicitly generated by the compiler. Such data types 844% can't be used in the variant part of a record. 845parser_e_resourcestring_only_sg=03152_E_?? ???? ?????? Resourcestring ???? ????? ??????, ?? ????? ??????? ?? ????? 846% Resourcestring can not be declared local, only global or using the static 847% directive. 848parser_e_exit_with_argument_not__possible=03153_E_?????? ?????? exit ???? ???? ?????? ?????? ?????? 849% an exit statement with an argument for the return value can't be used here, this 850% can happen e.g. in \var{try..except} or \var{try..finally} blocks 851parser_e_stored_property_must_be_boolean=03154_E_????? ??????? ?????? ?????? ???? ????? ??????? 852% If you specify a storage symbol in a property declaration, it must be of 853% the type boolean 854parser_e_ill_property_storage_sym=03155_E_?????? ???? ???? ????? ?????? ?????? 855% You can't use this type of symbol as storage specifier in property 856% declaration. You can use only methods with the result type boolean, 857% boolean class fields or boolean constants 858parser_e_only_publishable_classes_can_be_published=03156_E_?? ????? ??????? ???? $M+ ????? ????? ????? ? published 859% In the published section of a class can be only class as fields used which 860% are compiled in \var{\{\$M+\}} or which are derived from such a class. Normally 861% such a class should be derived from TPersitent 862parser_e_proc_directive_expected=03157_E_???? ??????? ????? 863% This error is triggered when you have a \var{\{\$Calling\}} directive without 864% a calling convention specified. 865% It also happens when declaring a procedure in a const block and you 866% used a ; after a procedure declaration which must be followed by a 867% procedure directive. 868% Correct declarations are: 869% \begin{verbatim} 870% const 871% p : procedure;stdcall=nil; 872% p : procedure stdcall=nil; 873% \end{verbatim} 874parser_e_invalid_property_index_value=03158_E_???? ??????? ?? ?????? ???? ????? ????? ????? 875% The value you use to index a property must be of an ordinal type, for 876% example an integer or enumerated type. 877parser_e_procname_to_short_for_export=03159_E_?? ????? ??? ???? ?????? 878% The length of the procedure/function name must be a…
Large files files are truncated, but you can click here to view the full file