#
#   This file is part of the Free Pascal Compiler
#   Copyright (c) 1999-2008 by the Free Pascal Development team
#
#   Hebrew (CP1255) language file for Free Pascal Compiler
#   Contributed by Ido Kanner <idokan at gmail.com> and Dotan Kamber <kamberd at yahoo.com>
#   Based on errore.msg of SVN revision 8988
#
#   See the file COPYING.v2, included in this distribution,
#   for details about the copyright.
#
#   This program is distributed in the hope that it will be useful,
#   but WITHOUT ANY WARRANTY; without even the implied warranty of
#   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
#
#
# The constants are build in the following order:
# <part>_<type>_<txtidentifier>
#
# <part> is the part of the compiler the message is used
#   asmr_     assembler parsing
#   asmw_     assembler writing/binary writers
#   unit_     unit handling
#   scan_     scanner
#   parser_   parser
#   type_     type checking
#   general_  general info
#   exec_     calls to assembler, linker, binder
#
# <type> the type of the message it should normally used for
#   f_   fatal error
#   e_   error
#   w_   warning
#   n_   note
#   h_   hint
#   i_   info
#   l_   add linenumber
#   u_   used
#   t_   tried
#   c_   conditional
#   d_   debug message
#   x_   executable informations
#

#
# General
#
# 01023 is the last used one
#
# BeginOfTeX
% \section{General compiler messages}
% This section gives the compiler messages which are not fatal, but which
% display useful information. The number of such messages can be
% controlled with the various verbosity level \var{-v} switches.
% \begin{description}
general_t_compilername=01000_T_????: $1
% When the \var{-vt} switch is used, this line tells you what compiler
% is used.
general_d_sourceos=01001_D_????? ?????: $1
% When the \var{-vd} switch is used, this line tells you what the source
% operating system is.
general_i_targetos=01002_I_????? ????? ??????: $1
% When the \var{-vd} switch is used, this line tells you what the target
% operating system is.
general_t_exepath=01003_T_????? ????? ????: $1
% When the \var{-vt} switch is used, this line tells you where the compiler
% looks for its binaries.
general_t_unitpath=01004_T_????? ????? ???????: $1
% When the \var{-vt} switch is used, this line tells you where the compiler
% looks for compiled units. You can set this path with the \var{-Fu}
general_t_includepath=01005_T_????? ????? ?????: $1
% When the \var{-vt} switch is used, this line tells you where the compiler
% looks for its include files (files used in \var{\{\$I xxx\}} statements).
% You can set this path with the \var{-I} option.
general_t_librarypath=01006_T_????? ????? ??????: $1
% When the \var{-vt} switch is used, this line tells you where the compiler
% looks for the libraries. You can set this path with the \var{-Fl} option.
general_t_objectpath=01007_T_Using object path: $1
% When the \var{-vt} switch is used, this line tells you where the compiler
% looks for object files you link in (files used in \var{\{\$L xxx\}} statements).
% You can set this path with the \var{-Fo} option.
general_i_abslines_compiled=01008_I_$1 ????? ?????, ?$2 ?????
% When the \var{-vi} switch is used, the compiler reports the number
% of lines compiled, and the time it took to compile them (real time,
% not program time).
general_f_no_memory_left=01009_F_?? ???? ?????
% The compiler doesn't have enough memory to compile your program. There are
% several remedies for this:
% \begin{itemize}
% \item If you're using the build option of the compiler, try compiling the
% different units manually.
% \item If you're compiling a huge program, split it up in units, and compile
% these separately.
% \item If the previous two don't work, recompile the compiler with a bigger
% heap (you can use the \var{-Ch} option for this, \seeo{Ch})
% \end{itemize}
general_i_writingresourcefile=01010_I_???? ?? ???? ????? ???? ????????: $1
% This message is shown when the compiler writes the Resource String Table
% file containing all the resource strings for a program.
general_e_errorwritingresourcefile=01011_E_???? ?? ???? ????? ???? ????????: $1
% This message is shown when the compiler encountered an error when writing
% the Resource String Table file
general_i_fatal=01012_I_????? ??????:
% Prefix for Fatal Errors
general_i_error=01013_I_?????:
% Prefix for Errors
general_i_warning=01014_I_?????:
% Prefix for Warnings
general_i_note=01015_I_????:
% Prefix for Notes
general_i_hint=01016_I_???:
% Prefix for Hints
general_e_path_does_not_exist=01017_E_????? "$1" ???? ????
% The specified path does not exist.
general_f_compilation_aborted=01018_F_?????? ????
% Compilation was aborted.
general_text_bytes_code=01019_bytes code
general_text_bytes_data=01020_bytes data
general_i_number_of_warnings=01021_I_?????? $1 ??????
% Total number of warnings issued during compilation.
general_i_number_of_hints=01022_I_??????  $1 ?????
% Total number of hints issued during compilation.
general_i_number_of_notes=01023_I_?????? $1 ?????
% Total number of notes issued during compilation.
% \end{description}
#
# Scanner
#
# 02084 is the last used one
#
% \section{Scanner messages.}
% This section lists the messages that the scanner emits. The scanner takes
% care of the lexical structure of the pascal file, i.e. it tries to find
% reserved words, strings, etc. It also takes care of directives and
% conditional compiling handling.
% \begin{description}
scan_f_end_of_file=02000_F_??? ???? ?? ????
% this typically happens in one of the following cases :
% \begin{itemize}
% \item The source file ends before the final \var{end.} statement. This
% happens mostly when the \var{begin} and \var{end} statements aren't
% balanced;
% \item An include file ends in the middle of a statement.
% \item A comment was not closed
% \end{itemize}
scan_f_string_exceeds_line=02001_F_?????? ????? ?????
% There is a missing closing ' in a string, so it occupies
% multiple lines.
scan_f_illegal_char=02002_F_?? ?? ???? "$1" ($2)
% An illegal character was encountered in the input file.
scan_f_syn_expected=02003_F_????? ?????: ???? ? "$1" ??? "$2" ????
% This indicates that the compiler expected a different token than
% the one you typed. It can occur almost everywhere where you make a
% mistake against the pascal language.
scan_t_start_include_file=02004_TL_????? ????? ?? ???? ?????? $1
% When you provide the \var{-vt} switch, the compiler tells you
% when it starts reading an included file.
scan_w_comment_level=02005_W_??? ????? $1 ?????
% When the \var{-vw} switch is used, then the compiler warns you if
% it finds nested comments. Nested comments are not allowed in Turbo Pascal
% and can be a possible source of errors.
scan_n_ignored_switch=02008_N_????? ???? ???? "$1"
% With \var{-vn} on, the compiler warns if it ignores a switch
scan_w_illegal_switch=02009_W_??? ???? "$1" ???? ????
% You included a compiler switch (i.e. \var{\{\$... \}}) which the compiler
% does not recognise
scan_w_switch_is_global=02010_W_????? ???? ???? ???? ??????
% The compiler switch is misplaced, and should be located at
% the start of the unit or program.
scan_e_illegal_char_const=02011_E_?? ???? ?? ????
% This happens when you specify a character with its ASCII code, as in
% \var{\#96}, but the number is either illegal, or out of range.
scan_f_cannot_open_input=02012_F_?? ???? ????? ?? ???? "$1"
% \fpc cannot find the program or unit source file you specified on the
% command line.
scan_f_cannot_open_includefile=02013_F_?? ???? ????? ?? ???? ??????? "$1"
% \fpc cannot find the source file you specified in a \var{\{\$include ..\}}
% statement.
scan_e_illegal_pack_records=02015_E_????? ????? ?? ???? ????? "$1"
% You are specifying the \var{\{\$PACKRECORDS n\} } or \var{\{\$ALIGN n\} }
% with an illegal value for \var{n}. For \$PACKRECORDS valid alignments are 1, 2, 4, 8, 16, 32, C,
% NORMAL, DEFAULT, and for \$ALIGN valid alignment are 1, 2, 4, 8, 16, 32, ON,
% OFF. Under mode MacPas \$ALIGN also supports MAC68K, POWER and RESET.
scan_e_illegal_pack_enum=02016_E_???? ??????? ?? ????? ?????? "$1" ???? ????
% You are specifying the \var{\{\$PACKENUM n\}} with an illegal value for
% \var{n}. Only 1,2,4, NORMAL or DEFAULT are valid here.
scan_e_endif_expected=02017_E_???? ?$ENDIF ?????? $1 $2 ?????? ?$3 ???? $4
% Your conditional compilation statements are unbalanced.
scan_e_preproc_syntax_error=02018_E_????? ????? ??? ????? ???? ????
% There is an error in the expression following the \var{\{\$if ..\}}, $ifc or $setc compiler
% directives.
scan_e_error_in_preproc_expr=02019_E_????? ???? ????
% There is an error in the expression following the \var{\{\$if ..\}}, $ifc or $setc compiler
% directives.
scan_w_macro_cut_after_255_chars=02020_W_???? ????? ????? ????? ?? 255 ?????
% The contents of macros cannot be longer than 255 characters.
scan_e_endif_without_if=02021_E_ENDIF ???  IF(N)DEF
% Your \var{\{\$IFDEF ..\}} and {\{\$ENDIF\}} statements aren't balanced.
scan_f_user_defined=02022_F_????? ?????: $1
% A user defined fatal error occurred. see also the \progref
scan_e_user_defined=02023_E_????? ?????: $1
% A user defined error occurred. see also the \progref
scan_w_user_defined=02024_W_????? ?????: $1
% A user defined warning occurred. see also the \progref
scan_n_user_defined=02025_N_????? ?????: $1
% A user defined note was encountered. see also the \progref
scan_h_user_defined=02026_H_????? ?????: $1
% A user defined hint was encountered. see also the \progref
scan_i_user_defined=02027_I_????? ?????: $1
% User defined information was encountered. see also the \progref
scan_e_keyword_cant_be_a_macro=02028_E_???? ???? ??????? ???? ????? ???? ????? ?????
% You cannot redefine keywords with macros.
scan_f_macro_buffer_overflow=02029_F_????? ???? ???? ??? ????? ?? ????? ?? ????
% Your macro or its result was too long for the compiler.
scan_w_macro_too_deep=02030_W_????? ???? ????? ????? ?? 16.
% When expanding a macro, macros have been nested to a level of 16.
% The compiler will expand no further, since this may be a sign that
% recursion is used.
scan_w_wrong_styled_switch=02031_W_ ???? ????? ???? ???? ?????? ?????? ???? //
% Compiler switches should be in normal pascal style comments.
scan_d_handling_switch=02032_DL_???? ???? "$1"
% When you set debugging info on (\var{-vd}) the compiler tells you when it
% is evaluating conditional compile statements.
scan_c_endif_found=02033_CL_???? ENDIF $1
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements.
scan_c_ifdef_found=02034_CL_???? IFDEF $1, $2
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements.
scan_c_ifopt_found=02035_CL_???? IFOPT $1, $2
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements.
scan_c_if_found=02036_CL_???? IF $1, $2
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements.
scan_c_ifndef_found=02037_CL_???? IFNDEF $1, $2
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements.
scan_c_else_found=02038_CL_???? ELSE $1, $2
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements.
scan_c_skipping_until=02039_CL_????...
% When you turn on conditional messages(\var{-vc}), the compiler tells you
% where it encounters conditional statements, and whether it is skipping or
% compiling parts.
scan_i_press_enter=02040_I_??? ?? <return> ??????
% When the \var{-vi} switch is used, the compiler stops compilation
% and waits for the \var{Enter} key to be pressed when it encounters
% a \var{\{\$STOP\}} directive.
scan_w_unsupported_switch=02041_W_??? "$1" ???? ????
% When warnings are turned on (\var{-vw}) the compiler warns you about
% unsupported switches. This means that the switch is used in Delphi or
% Turbo Pascal, but not in \fpc
scan_w_illegal_directive=02042_W_????? ????? "$1" ???? ?????
% When warings are turned on (\var{-vw}) the compiler warns you about
% unrecognised switches. For a list of recognised switches, \progref
scan_t_back_in=02043_TL_???? ?$1
% When you use (\var{-vt}) the compiler tells you when it has finished
% reading an include file.
scan_w_unsupported_app_type=02044_W_??? ????? ???? ?????????: "$1"
% You get this warning, if you specify an unknown application type
% with the directive \var{\{\$APPTYPE\}}
scan_w_app_type_not_support=02045_W_APPTYPE ???? ???? ?"? ??????? ????? ???????
% The \var{\{\$APPTYPE\}} directive is supported by certain operating systems only.
scan_w_description_not_support=02046_W_DESCRIPTION ???? ???? ?"? ????? ?????? ???????
% The \var{\{\$DESCRIPTION\}} directive is not supported on this target OS
scan_n_version_not_support=02047_N_VERSION ???? ???? ?"? ????? ????? ???????
% The \var{\{\$VERSION\}} directive is not supported on this target OS
scan_n_only_exe_version=02048_N_VERSION ?? ????? exe ?? DLL
% The \var{\{\$VERSION\}} directive is only used for executable or DLL sources.
scan_w_wrong_version_ignored=02049_W_????? ???? ?????? VERSION: "$1"
% The \var{\{\$VERSION\}} directive format is majorversion.minorversion
% where majorversion and minorversion are words.
scan_e_illegal_asmmode_specifier=02050_E_????? ??????? ?????? "$1" ???? ????
% When you specify an assembler mode with the \var{\{\$ASMMODE xxx\}}
% the compiler didn't recognize the mode you specified.
scan_w_no_asm_reader_switch_inside_asm=02051_W_??? ???? ?ASM ???? ????? ???? ???? ??????. "$1" ???? ????? ?? ?????? ????/
% It is not possible to switch from one assembler reader to another
% inside an assembler block. The new reader will be used for next
% assembler statements only.
scan_e_wrong_switch_toggle=02052_E_????? ???? ????. ????? ?ON/OFF ?? ? +/-
% You need to use ON or OFF or a + or - to toggle the switch
scan_e_resourcefiles_not_supported=02053_E_???? ??????? ???? ???? ???? ?????
% The target you are compiling for doesn't support resource files.
scan_w_include_env_not_found=02054_W_????? ?????? "$1" ?? ???? ??????
% The included environment variable can't be found in the environment, it will
% be replaced by an empty string instead.
scan_e_invalid_maxfpureg_value=02055_E_??? ?? ???? ??????? ???? ?FPC
% Valid values for this directive are 0..8 and NORMAL/DEFAULT
scan_w_only_one_resourcefile_supported=02056_W_?? ???? ?????? ??? ???? ???? ??
% The target you are compiling for supports only one resource file.
% The first resource file found is used, the others are discarded.
scan_w_macro_support_turned_off=02057_W_?????? ????? ????
% A macro declaration has been found, but macro support is currently off,
% so the declaration will be ignored. To turn macro support on compile with
% -Sm on the commandline or add \{\$MACRO ON\} in the source
scan_e_invalid_interface_type=02058_E_????? ??? ???? ?? ????. ?????? ?????? ?? COM, CORBA ?? DEFAULT
% The interface type that was specified is not supported
scan_w_appid_not_support=02059_W_APPID ???? ?? ?PALMOS
% The \var{\{\$APPID\}} directive is only supported for the PalmOS target.
scan_w_appname_not_support=02060_W_APPNAME ???? ?? ?PALMOS
% The \var{\{\$APPNAME\}} directive is only supported for the PalmOS target.
scan_e_string_exceeds_255_chars=02061_E_?????? ????? ?? ????? ????? ??? 255 ?????
% A single string constant can contain at most 255 chars. Try splitting up the
% string in multiple smaller parts and concatenate them with a + operator.
scan_f_include_deep_ten=02062_F_????? ???? ?include ??? ????? ?16
% When including include files the files have been nested to a level of 16.
% The compiler will expand no further, since this may be a sign that
% recursion is used.
scan_e_too_many_push=02063_F_???? ???? ????? PUSH
% A maximum of 20 levels is allowed. This error occurs only in mode MacPas.
scan_e_too_many_pop=02064_E_POP ??? ????? ?? PUSH
% This error occurs only in mode MacPas.
scan_e_error_macro_lacks_value=02065_E_???? "$1" ?? ???? ?????
% Thus the conditional compile time expression cannot be evaluated.
scan_e_wrong_switch_toggle_default=02066_E_????? ???? ????, ????? ? ON/OFF/DEFAULT ?? ?+/-/*
% You need to use ON or OFF or DEFAULT or a + or - or * to toggle the switch
scan_e_mode_switch_not_allowed=02067_E_??? ??? "$1" ?? ?????
% A mode switch has already been encountered, or, in case of option -Mmacpas,
% a mode switch occur after UNIT.
scan_e_error_macro_undefined=02068_E_????? ??? ????? "$1" ?? ?????.
% Thus the conditional compile time expression cannot be evaluated. Only in mode MacPas.
scan_e_utf8_bigger_than_65535=02069_E_???? ??? UTF-8 ????? ???? ?65535
% \fpc handles utf-8 strings internally as widestrings e.g. the char codes are limited to 65535
scan_e_utf8_malformed=02070_E_?????? UTF-8 ?????
% The given string isn't a valid UTF-8 string
scan_c_switching_to_utf8=02071_C_UTF-8 signature found, using UTF-8 encoding
% The compiler found an UTF-8 encoding signature (\$ef, \$bb, \$bf) at the beginning of a file,
% so it interprets it as an UTF-8 file
scan_e_compile_time_typeerror=02072_E_????? ???? ?????: ???? $1 ??? ????? $2 ?$3
% Type check of a compile time expression failed.
scan_n_app_type_not_support=02073_N_APPTYPE ?? ???? ?????? ?????? ???????
% The \var{\{\$APPTYPE\}} directive is supported by certain operating systems only.
scan_e_illegal_optimization_specifier=02074_E_???? ????? ?? ???? "$1"
% When you specify an optimization with the \var{\{\$OPTIMIZATION xxx\}}
% the compiler didn't recognize the optimization you specified.
scan_w_setpeflags_not_support=02075_W_SETPEFLAGS ???? ???? ?????? ?????? ???????
% The \var{\{\$SETPEFLAGS\}} directive is not supported by the target OS
scan_w_imagebase_not_support=02076_W_IMAGEBASE ???? ???? ?? ??? ????? ?????? ???????
% The \var{\{\$IMAGEBASE\}} directive is not supported by the target OS
scan_w_minstacksize_not_support=02077_W_MINSTACKSIZE ???? ???? ?? ??? ????? ?????? ???????
% The \var{\{\$MINSTACKSIZE\}} directive is not supported by the target OS
scan_w_maxstacksize_not_support=02078_W_MAXSTACKSIZE ???? ???? ?? ??? ????? ?????? ???????
% The \var{\{\$MAXSTACKSIZE\}} directive is not supported by the target OS
scanner_e_illegal_warn_state=02079_E_????? ?? ???? ?????? $WARN
% Only ON and OFF can be used as state with a \$warn compiler directive
scan_e_only_packset=02080_E_??? ?? ????? ?? ????
% Only 0, 1, 2, 4, 8, DEFAULT and NORMAL are allowed as packset parameter
scan_w_pic_ignored=02081_W_????? ?????? PIC
% Several targets like windows do not support neither need PIC so the PIC directive and switch are
% ignored.
scan_w_unsupported_switch_by_target=02082_W_???? "$1" ???? ???? ???? ????? ?????
% Some compiler switches like \$E are not supported by all targets.
scan_w_frameworks_darwin_only=02084_W_???????? ??????? ????? ?????? ?? ???? Darwin/Mac OS X
% Frameworks are not a known concept, or at least not supported by FPC, on operating systems other than Darwin/Mac OS X.
scan_e_illegal_minfpconstprec=02085_E_???? ???? ????? ?? ?????? ???????? ????????? "$1" ???? ????
% 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.
% \end{description}
#
# Parser
#
# 03192 is the last used one
#
% \section{Parser messages}
% This section lists all parser messages. The parser takes care of the
% semantics of you language, i.e. it determines if your pascal constructs
% are correct.
% \begin{description}
parser_e_syntax_error=03000_E_???? - ????? ???????
% An error against the Turbo Pascal language was encountered. This happens
% typically when an illegal character is found in the sources file.
parser_e_dont_nest_interrupt=03004_E_???????? ????? ???? ????? ????? ??????
% An \var{INTERRUPT} procedure must be global.
parser_w_proc_directive_ignored=03005_W_????? ???? ???????? "$1"
% The specified procedure directive is ignored by FPC programs.
parser_e_no_overload_for_all_procs=03006_E_?? ?? ??????? ?? "$1" ????? ????? OVERLOAD
% When you want to use overloading using the \var{OVERLOAD} directive, then
% all declarations need to have \var{OVERLOAD} specified.
parser_e_export_name_double=03008_E_???????? ?????? ?? ???????? "$1"
% Exported function names inside a specific DLL must all be different
parser_e_export_ordinal_double=03009_E_???????? ?????? ?????? ???????? "$1"
% Exported function names inside a specific DLL must all be different
parser_e_export_invalid_index=03010_E_?????? ?? ???? ?????? ????????
% DLL function index must be in the range \var{1..\$FFFF}
parser_w_parser_reloc_no_debug=03011_W_????? ????? ????? ?????? ?? ?????? ????? DLL ?? ???? ????. ?????.
parser_w_parser_win32_debug_needs_WN=03012_W_????? ????? ?????? ?win32 ?? ???? ?? ????? ?????? ?"? ??????? -WN
% Stabs info is wrong for relocatable DLL or EXES use -WN
% if you want to debug win32 executables.
parser_e_constructorname_must_be_init=03013_E_?? ???? ???? ????? INIT
% You are declaring an object constructor with a name which is not \var{init}, and the
% \var{-Ss} switch is in effect. See the \var{-Ss} switch (\seeo{Ss}).
parser_e_destructorname_must_be_done=03014_E_?? ???? ???? ????? DONE
% You are declaring an object destructor with a name which is not \var{done}, and the
% \var{-Ss} switch is in effect. See the \var{-Ss} switch (\seeo{Ss}).
parser_e_proc_inline_not_supported=03016_E_???????? INLINE ?? ?????
% You tried to compile a program with C++ style inlining, and forgot to
% specify the \var{-Si} option (\seeo{Si}). The compiler doesn't support C++
% styled inlining by default.
parser_w_constructor_should_be_public=03018_W_???? ???? ????? ??????
% Constructors must be in the 'public' part of an object (class) declaration.
parser_w_destructor_should_be_public=03019_W_???? ???? ????? ??????
% Destructors must be in the 'public' part of an object (class) declaration.
parser_n_only_one_destructor=03020_N_????? ????? ???? ??? ????
% You can declare only one destructor for a class.
parser_e_no_local_objects=03021_E_?????? ????? ??????? ???? ??????
% Classes must be defined globally. They cannot be defined inside a
% procedure or function
parser_f_no_anonym_objects=03022_F_?????? ????? ????????? ???? ??????
% An invalid object (class) declaration was encountered, i.e. an
% object or class without methods that isn't derived from another object or
% class. For example:
% \begin{verbatim}
% Type o = object
%          a : longint;
%          end;
% \end{verbatim}
% will trigger this error.
parser_n_object_has_no_vmt=03023_N_???????? "$1" ??? VMT
% This is a note indicating that the declared object has no
% virtual method table.
parser_e_illegal_parameter_list=03024_E_????? ??????? ?? ?????
% You are calling a function with parameters that are of a different type than
% the declared parameters of the function.
parser_e_wrong_parameter_size=03026_E_???? ???? ?? ??????? ???? ???? ?????? ? "$1"
% There is an error in the parameter list of the function or procedure,
% the number of parameters is not correct.
parser_e_overloaded_no_procedure=03027_E_???? ?????? ????? "$1" ???? ???????
% The compiler encountered a symbol with the same name as an overloaded
% function, but it is not a function it can overload.
parser_e_overloaded_have_same_parameters=03028_E_???????? ?????? ????? ?????? ?? ???? ????? ???????
% You're declaring overloaded functions, but with the same parameter list.
% Overloaded function must have at least 1 different parameter in their
% declaration.
parser_e_header_dont_match_forward=03029_E_????? ???????? ???? ????? ?? ?????? ?????? "$1"
% You declared a function with same parameters but
% different result type or function modifiers.
parser_e_header_different_var_names=03030_E_????? ???????? "$1" ???? ????? ?? ??????: ?? ????? ????? $2 => $3
% You declared the function in the \var{interface} part, or with the
% \var{forward} directive, but define it with a different parameter list.
parser_n_duplicate_enum=03031_N_????? ???? ???? ?????? ????? ???? ????
% \fpc allows enumeration constructions as in C. Given the following
% declaration two declarations:
% \begin{verbatim}
% type a = (A_A,A_B,A_E:=6,A_UAS:=200);
% type a = (A_A,A_B,A_E:=6,A_UAS:=4);
% \end{verbatim}
% The second declaration would produce an error. \var{A\_UAS} needs to have a
% value higher than \var{A\_E}, i.e. at least 7.
parser_e_no_with_for_variable_in_other_segments=03033_E_With ???? ????? ?????? ??????? ????? ????
% With stores a variable locally on the stack,
% but this is not possible if the variable belongs to another segment.
parser_e_too_much_lexlevel=03034_E_??????? ?????? > 31
% You can nest function definitions only 31 times.
parser_e_range_check_error=03035_E_????? ?????? ???? ??? ????? ??????
% The constants are out of their allowed range.
parser_w_range_check_error=03036_W_????? ?????? ???? ??? ????? ??????
% The constants are out of their allowed range.
parser_e_double_caselabel=03037_E_????? ????? ????? ?case
% You are specifying the same label 2 times in a \var{case} statement.
parser_e_case_lower_less_than_upper_bound=03038_E_????? ????? ??? ?????? ???????
% The upper bound of a \var{case} label is less than the lower bound and this
% is useless
parser_e_type_const_not_possible=03039_E_????? ????? ?????? ?? ?????? ?? ?????? ?????
% You cannot declare a constant of type class or object.
parser_e_no_overloaded_procvars=03040_E_?????? ?? ???????? ?????? ????? ???? ??????
% You are trying to assign an overloaded function to a procedural variable.
% This is not allowed
parser_e_invalid_string_size=03041_E_???? ?????? ???? ????? ?? ????? ?1 ?255
% The length of a shortstring in Pascal is limited to 255 characters. You are
% trying to declare a string with length lower than 1 or greater than 255
parser_w_use_extended_syntax_for_objects=03042_W_????? ?????? ????? ?? NEW ?DISPOSE ??????? ?? ???????
% If you have a pointer \var{a} to a class type, then the statement
% \var{new(a)} will not initialize the class (i.e. the constructor isn't
% called), although space will be allocated. you should issue the
% \var{new(a,init)} statement. This will allocate space, and call the
% constructor of the object
parser_w_no_new_dispose_on_void_pointers=03043_W_?????? ?????? ?? ????? ?? NEW ? DISPOSE ??? ??????
parser_e_no_new_dispose_on_void_pointers=03044_E_???? ????? ?????? ?????? ?? ????? ?? NEW ?? DISPOSE
% You cannot use \var{new(p)} or \var{dispose(p)} if \var{p} is an untyped pointer
% because no size is associated to an untyped pointer.
% Accepted for compatibility in \var{tp} and \var{delphi} modes.
parser_e_class_id_expected=03045_E_???? ????? ?????
% This happens when the compiler scans a procedure declaration that contains
% a dot,
% i.e., a object or class method, but the type in front of the dot is not
% a known type.
parser_e_no_type_not_allowed_here=03046_E_??? ???? ?? ????? ?????? ??????
% You cannot use a type inside an expression.
parser_e_methode_id_expected=03047_E_???? ????? ?????
% This identifier is not a method.
% This happens when the compiler scans a procedure declaration that contains
% a dot, i.e., a object or class method, but the procedure name is not a
% procedure of this type.
parser_e_header_dont_match_any_member=03048_E_????? ???????? ?? ??? ??????? ?? ?????? "$1"
% This identifier is not a method.
% This happens when the compiler scans a procedure declaration that contains
% a dot, i.e., a object or class method, but the procedure name is not a
% procedure of this type.
parser_d_procedure_start=03049_DL_????????/??????? $1
% When using the \var{-vd} switch, the compiler tells you when it starts
% processing a procedure or function implementation.
parser_e_error_in_real=03050_E_???? ?? ???? ???? ???? ????
% The compiler expects a floating point expression, and gets something else.
parser_e_fail_only_in_constructor=03051_E_FAIL ???? ????? ?????? ?? ???? ????
% You are using the \var{fail} keyword outside a constructor method.
parser_e_no_paras_for_destructor=03052_E_?????? ?? ?????? ????? ???????
% You are declaring a destructor with a parameter list. Destructor methods
% cannot have parameters.
parser_e_only_class_methods_via_class_ref=03053_E_?? ?????? ????? ?????? ????? ??????? ????????? ?????
% This error occurs in a situation like the following:
% \begin{verbatim}
% Type :
%    Tclass = Class of Tobject;
%
% Var C : TClass;
%
% begin
% ...
% C.free
% \end{verbatim}
% \var{Free} is not a class method and hence cannot be called with a class
% reference.
parser_e_only_class_methods=03054_E_?? ????? ????? ????? ???? ?????? ?????
% This is related to the previous error. You cannot call a method of an object
% from a inside a class method. The following code would produce this error:
% \begin{verbatim}
% class procedure tobject.x;
%
% begin
%   free
% \end{verbatim}
% Because free is a normal method of a class it cannot be called from a class
% method.
parser_e_case_mismatch=03055_E_?????? ???? CASE ???? ???????
% One of the labels is not of the same type as the case variable.
parser_e_illegal_symbol_exported=03056_E_?? ???? ????? ?? ???? ???????
% You can only export procedures and functions when you write a library. You
% cannot export variables or constants.
parser_w_should_use_override=03057_W_????? ????? ????? ?"? "$1"
% A method that is declared \var{virtual} in a parent class, should be
% overridden in the descendent class with the \var{override} directive. If you
% don't specify the \var{override} directive, you will hide the parent method;
% you will not override it.
parser_e_nothing_to_be_overridden=03058_E_??? ?????  ?????? ?? ??? ??? ???? ?????: "$1"
% You are trying to \var{override} a virtual method of a parent class that does
% not exist.
parser_e_no_procedure_to_access_property=03059_E_?? ???? ???? ???? ???????
% You specified no \var{read} directive for a property.
parser_w_stored_not_implemented=03060_W_?????? ???? ???? ????? ?????
% The \var{stored} directive is not yet implemented
parser_e_ill_property_access_sym=03061_E_???? ?? ???? ????? ???????
% There is an error in the \var{read} or \var{write} directives for an array
% property. When you declare an array property, you can only access it with
% procedures and functions. The following code would cause such an error.
% \begin{verbatim}
% tmyobject = class
%   i : integer;
%   property x [i : integer]: integer read I write i;
% \end{verbatim}
%
parser_e_cant_access_protected_member=03062_E_?? ???? ???? ???? ???? ???????? ??????
% Fields that are declared in a \var{protected} section of an object or class
% declaration cannot be accessed outside the module where the object is
% defined, or outside descendent object methods.
parser_e_cant_access_private_member=03063_E_?? ???? ???? ???? ???? ???????? ??????
% Fields that are declared in a \var{private} section of an object or class
% declaration cannot be accessed outside the module where the class is
% defined.
parser_e_overridden_methods_not_same_ret=03066_E_????? ????? ????? ????? ????? ??? ???? ??????: "$2" ?????? ?"? "$1", ??? ????? ??? ????? ???
% If you declare overridden methods in a class definition, they must
% have the same return type.
parser_e_dont_nest_export=03067_E_?????? ???????? EXPORT ?? ?????? ????? ???????
% You cannot declare a function or procedure within a function or procedure
% that was declared as an export procedure.
parser_e_methods_dont_be_export=03068_E_?? ???? ????? ?? ??????
% You cannot declare a procedure that is a method for an object as
% \var{export}ed.
parser_e_call_by_ref_without_typeconv=03069_E_?????? ?????? ?? ????? ???? ????? ???: ???? "$1" ???? ?"$2"
% When calling a function declared with \var{var} parameters, the variables in
% the function call must be of exactly the same type. There is no automatic
% type conversion.
parser_e_no_super_class=03070_E_?????? ????? ????? ?? ?? ?????? ???????
% When calling inherited methods, you are trying to call a method of a non-related
% class. You can only call an inherited method of a parent class.
parser_e_self_not_in_method=03071_E_SELF ????? ?? ???????
% You are trying to use the \var{self} parameter outside an object's method.
% Only methods get passed the \var{self} parameters.
parser_e_generic_methods_only_in_methods=03072_E_?????? ?????? ?????? ?????? ?? ???? ?????? ????? ?? ??? ???? ????????
% A construction like \var{sometype.somemethod} is only allowed in a method.
parser_e_illegal_colon_qualifier=03073_E_????? ?? ???? ?? ':'
% You are using the format \var{:} (colon) 2 times on an expression that
% is not a real expression.
parser_e_illegal_set_expr=03074_E_????? ?????? ???? ????? ?????? ?? ????? ????
% The declaration of a set contains an error. Either one of the elements is
% outside the range of the set type, either two of the elements are in fact
% the same.
parser_e_pointer_to_class_expected=03075_E_???? ?????? ???????
% You specified an illegal type in a \var{new} statement.
% The extended syntax of \var{new} needs an object as a parameter.
parser_e_expr_have_to_be_constructor_call=03076_E_?????? ???? ????? ????? ????
% When using the extended syntax of \var{new}, you must specify the constructor
% method of the object you are trying to create. The procedure you specified
% is not a constructor.
parser_e_expr_have_to_be_destructor_call=03077_E_?????? ???? ????? ????? ????
% When using the extended syntax of \var{dispose}, you must specify the
% destructor method of the object you are trying to dispose of.
% The procedure you specified is not a destructor.
parser_e_invalid_record_const=03078_E_??? ?? ???? ?? ??????? ??????
% When declaring a constant record, you specified the fields in the wrong
% order.
parser_e_false_with_expr=03079_E_??? ????? ???? ????? ????? ????? ?? ?????
% A \var{with} statement needs an argument that is of the type \var{record}
% or \var{class}. You are using \var{with} on an expression that is not of
% this type.
parser_e_void_function=03080_E_???????? ?? ????? ?????? ???
% In \fpc, you can specify a return value for a function when using
% the \var{exit} statement. This error occurs when you try to do this with a
% procedure. Procedures cannot return a value.
parser_e_only_methods_allowed=03081_E_??????? ???????? ?????? ????? ???????
% You're declaring a procedure as destructor, constructor or class operator, when the
% procedure isn't a class method.
parser_e_operator_not_overloaded=03082_E_????????? ?? ????? ?????
% You're trying to use an overloaded operator when it is not overloaded for
% this type.
parser_e_no_such_assignment=03083_E_?? ???? ????? ????? ?????? ????? ?????
% You can not overload assignment for types
% that the compiler considers as equal.
parser_e_overload_impossible=03084_E_???? ????? ?????? ???????? ????? ?????
% The combination of operator, arguments and return type are
% incompatible.
parser_e_no_reraise_possible=03085_E_?? ???? ????? ?????
% You are trying to raise an exception where it is not allowed. You can only
% raise exceptions in an \var{except} block.
parser_e_no_new_or_dispose_for_classes=03086_E_?????? ?????? ?? NEW ?? DISPOSE ?? ????? ???????
% You cannot generate an instance of a class with the extended syntax of
% \var{new}. The constructor must be used for that. For the same reason, you
% cannot call \var{dispose} to de-allocate an instance of a class, the
% destructor must be used for that.
parser_e_procedure_overloading_is_off=03088_E_??????? ?????????? ?????? ????? ????
% When using the \var{-So} switch, procedure overloading is switched off.
% Turbo Pascal does not support function overloading.
parser_e_overload_operator_failed=03089_E_?? ???? ?????? ?? ??? ???????? ??????. ????? ?????????? ??????? ?????? (?? ????) ??: $1
% You are trying to overload an operator which cannot be overloaded.
% The following operators can be overloaded :
% \begin{verbatim}
%    +, -, *, /, =, >, <, <=, >=, is, as, in, **, :=
% \end{verbatim}
parser_e_comparative_operator_return_boolean=03090_E_??????? ??????? ???? ?????? ??? ???????
% When overloading the \var{=} operator, the function must return a boolean
% value.
parser_e_only_virtual_methods_abstract=03091_E_?? ???? ?????????? ????? ????? ?????
% You are declaring a method as abstract, when it is not declared to be
% virtual.
parser_f_unsupported_feature=03092_F_????? ??????? ?? ?????!
% You're trying to force the compiler into doing something it cannot do yet.
parser_e_mix_of_classes_and_objects=03093_E_?????? ?? ????? ????? (??????, ???, ???? ???') ???? ?????
% You cannot derive \var{objects}, \var{classes}, \var{cppclasses} and \var{interfaces} interttwined . E.g.
% a class cannot have an object as parent and vice versa.
parser_w_unknown_proc_directive_ignored=03094_W_????? ?????? ?????: "$1"
% The procedure directive you specified is unknown.
parser_e_absolute_only_one_var=03095_E_absolute ???? ?????? ?? ?? ????? ???
% You cannot specify more than one variable before the \var{absolute} directive.
% Thus, the following construct will provide this error:
% \begin{verbatim}
% Var Z : Longint;
%     X,Y : Longint absolute Z;
% \end{verbatim}
% \item [ absolute can only be associated a var or const ]
% The address of a \var{absolute} directive can only point to a variable or a
% typed constant. Therefore, the following code will produce this error:
% \begin{verbatim}
%   Procedure X;
%
%  var p : longint absolute x;
% \end{verbatim}
%
parser_e_absolute_only_to_var_or_const=03096_E_???? ?????? ?absolute ?? ?? ????? ?? ????
% The address of a \var{absolute} directive can only point to a variable or
% constant. Therefore, the following code will produce this error:
% \begin{verbatim}
%   Procedure X;
%
%  var p : longint absolute x;
% \end{verbatim}
%
parser_e_initialized_only_one_var=03097_E_???? ????? ?? ????? ???
% You cannot specify more than one variable with a initial value
% in Delphi mode.
parser_e_abstract_no_definition=03098_E_????? ?????? ???? ????? ?????? (?? ??? ?? ???????)
% Abstract methods can only be declared, you cannot implement them. They
% should be overridden by a descendant class.
parser_e_overloaded_must_be_all_global=03099_E_????? ???? ?? ???????? ???? ????? ????? ?????? (????? ????? ??????)
% You are defining a overloaded function in the implementation part of a unit,
% but there is no corresponding declaration in the interface part of the unit.
parser_w_virtual_without_constructor=03100_W_????? ??????? ??????????? ??? ???? ? "$1"
% If you declare objects or classes that contain virtual methods, you need
% to have a constructor and destructor to initialize them. The compiler
% encountered an object or class with virtual methods that doesn't have
% a constructor/destructor pair.
parser_c_macro_defined=03101_CL_????? ?????: $1
% When \var{-vc} is used, the compiler tells you when it defines macros.
parser_c_macro_undefined=03102_CL_????? ?? ?????: $1
% When \var{-vc} is used, the compiler tells you when it undefines macros.
parser_c_macro_set_to=03103_CL_????? $1 ????? ? $2
% When \var{-vc} is used, the compiler tells you what values macros get.
parser_i_compiling=03104_I_???? $1
% When you turn on information messages (\var{-vi}), the compiler tells you
% what units it is recompiling.
parser_u_parsing_interface=03105_UL_???? ?? ????? ?? ?????? $1
% This tells you that the reading of the interface
% of the current unit starts
parser_u_parsing_implementation=03106_UL_???? ?? ?????? ?? $1
% This tells you that the code reading of the implementation
% of the current unit, library or program starts
parser_d_compiling_second_time=03107_DL_???? ?? $1 ???? ??????
% When you request debug messages (\var{-vd}) the compiler tells you what
% units it recompiles for the second time.
parser_e_no_property_found_to_override=03109_E_?? ????? ????? ??????
% You want to override a property of a parent class, when there is, in fact,
% no such property in the parent class.
parser_e_only_one_default_property=03110_E_?? ????? ??? ?? ????? ???? ?????
% You specified a property as \var{Default}, but the class already has a
% default property, and a class can have only one default property.
parser_e_property_need_paras=03111_E_????? ?? ????? ???? ????? ????? ????? ?? ????
% Only array properties of classes can be made \var{default} properties.
parser_e_constructor_cannot_be_not_virtual=03112_E_?????? ?????????? ?????? ?? ??????
% You cannot have virtual constructors in objects. You can only have them
% in classes.
parser_e_no_default_property_available=03113_E_??? ????? ???? ???? ???? ??????
% You are trying to access a default property of a class, but this class (or one of
% its ancestors) doesn't have a default property.
parser_e_cant_have_published=03114_E_?????? ???? ????? ????? ?? ??? published, ????? ???? {$M+}
% If you want a \var{published} section in a class definition, you must
% use the \var{\{\$M+\}} switch, whch turns on generation of type
% information.
parser_e_forward_declaration_must_be_resolved=03115_E_????? ????? ??????? ?? ?????? "$1" ???? ?????? ?? ?????? ?????
% To be able to use an object as an ancestor object, it must be defined
% first. This error occurs in the following situation:
% \begin{verbatim}
%  Type ParentClas = Class;
%       ChildClass = Class(ParentClass)
%         ...
%       end;
% \end{verbatim}
% Where \var{ParentClass} is declared but not defined.
parser_e_no_local_operator=03116_E_?????? ????????? ????? ???? ????
% You cannot overload locally, i.e. inside procedures or function
% definitions.
parser_e_proc_dir_not_allowed_in_interface=03117_E_???? ????? "$1" ???? ????? ?????? ???? ?????
% This procedure directive is not allowed in the \var{interface} section of
% a unit. You can only use it in the \var{implementation} section.
parser_e_proc_dir_not_allowed_in_implementation=03118_E_???? ????? "$1" ???? ????? ???? ???????
% This procedure directive is not defined in the \var{implementation} section of
% a unit. You can only use it in the \var{interface} section.
parser_e_proc_dir_not_allowed_in_procvar=03119_E_???? ????? "$1" ???? ????? ???? ?????? ??????
% This procedure directive cannot be part of a procedural or function
% type declaration.
parser_e_function_already_declared_public_forward=03120_E_????? ???????? "$1" ??? ?????
% You will get this error if a function is defined as \var{forward} twice.
% Or it is once in the \var{interface} section, and once as a \var{forward}
% declaration in the \var{implmentation} section.
parser_e_not_external_and_export=03121_E_?? ???? ?????? ?? ? EXPORT ??? EXTERNAL
% These two procedure directives are mutually exclusive
parser_h_not_supported_for_inline=03123_H_"$1" ???? ???? ????? ???? ???????/???? inline
% Inline procedures don't support this declaration.
parser_h_inlining_disabled=03124_H_?????? ????? ?????
% Inlining of procedures is disabled.
parser_i_writing_browser_log=03125_I_???? ???? ????? $1
% When information messages are on, the compiler warns you when it
% writes the browser log (generated with the \var{\{\$Y+ \}} switch).
parser_h_maybe_deref_caret_missing=03126_H_????? ?? ??? ???? ??????
% The compiler thinks that a pointer may need a dereference.
parser_f_assembler_reader_not_supported=03127_F_??? ????? ????? ?????
% The selected assembler reader (with \var{\{\$ASMMODE xxx\}} is not
% supported. The compiler can be compiled with or without support for a
% particular assembler reader.
parser_e_proc_dir_conflict=03128_E_???? ?????? "$1" ????? ?? ?????? ?????
% You specified a procedure directive that conflicts with other directives.
% for instance \var{cdecl} and \var{pascal} are mutually exclusive.
parser_e_call_convention_dont_match_forward=03129_E_?????? ?????? ??????? ???? ??? ?????? ????????
% This error happens when you declare a function or procedure with
% e.g. \var{cdecl;} but omit this directive in the implementation, or vice
% versa. The calling convention is part of the function declaration, and
% must be repeated in the function definition.
parser_e_property_cant_have_a_default_value=03131_E_?????? ???? ?????? ????? ??? ????? ????
% Set properties or indexed properties cannot have a default value.
parser_e_property_default_value_must_const=03132_E_??? ????? ?????? ?? ?????? ???? ????? ????
% The value of a \var{default} declared property must be known at compile
% time. The value you specified is only known at run time. This happens
% .e.g. if you specify a variable name as a default value.
parser_e_cant_publish_that=03133_E_???? ???? ???? ????? ?????? ???? ????? ??? ?????? ???? ??????
% Only class type variables can be in a \var{published} section of a class
% if they are not declared as a property.
parser_e_cant_publish_that_property=03134_E_??? ?? ?? ????? ???? ???? ????? ??????
% Properties in a \var{published} section cannot be array properties.
% they must be moved to public sections. Properties in a \var{published}
% section must be an ordinal type, a real type, strings or sets.
parser_e_empty_import_name=03136_E_???? ?? ?????
% Some targets need a name for the imported procedure or a \var{cdecl} specifier
parser_e_division_by_zero=03138_E_???? ????
% There is a division by zero encounted
parser_e_invalid_float_operation=03139_E_????? ??????? ?? ?????
% An operation on two real type values produced an overflow or a division
% by zero.
parser_e_array_lower_less_than_upper_bound=03140_E_????? ?????? ???? ???? ?????? ??????
% The upper bound of a an array declaration is less than the lower bound and this
% is not possible
parser_w_string_too_long=03141_W_???? ??????? ?? "$1" ???? ???? ? "$1"
% The size of the constant string is larger than the size you specified in
% string type definition
parser_e_string_larger_array=03142_E_???? ??????? ???? ???? ????? ???? ??????
% The size of the constant string is larger than the size you specified in
% the array[x..y] of char definition
parser_e_ill_msg_expr=03143_E_????? ?? ?????? ???? ?????? ???? ????
% \fpc supports only integer or string values as message constants
parser_e_ill_msg_param=03144_E_????? ??????? ???? ????? ????? ???? ?? ???????
% A method declared with the \var{message}-directive as message handler
% can take only one parameter which must be declared as call by reference
% Parameters are declared as call by reference using the \var{var}-directive
parser_e_duplicate_message_label=03145_E_????? ????? ?????: "$1"
% A label for a message is used twice in one object/class
parser_e_self_in_non_message_handler=03146_E_Self ???? ????? ????? ?????? ?? ???? ???????
% The self parameter can only be passed explicitly to a method which
% is declared as message handler.
parser_e_threadvars_only_sg=03147_E_Threadvars ?????? ????? ?????? ?? ????????
% Threadvars must be static or global, you can't declare a thread
% local to a procedure. Local variables are always local to a thread,
% because every thread has its own stack and local variables
% are stored on the stack
parser_f_direct_assembler_not_allowed=03148_F_?????? ????? ?????? ???? ???? ???? ?????? ????????
% You can't use direct assembler when using a binary writer, choose an
% other outputformat or use another assembler reader
parser_w_no_objpas_use_mode=03149_W_???? ????? ?????? OBJPAS ??????, ?? ?????? ? \{\$mode objfpc\} ?? ? \{\$mode delphi\} ?????
% You are trying to load the ObjPas unit manually from a uses clause. This is
% not a good idea. Use the \var{\{\$mode objfpc\}} or
% \var{\{\$mode delphi\}}
% directives which load the unit automatically
parser_e_no_object_override=03150_E_OVERRIDE ???? ???? ????? ?????? ??????????
% Override is not supported for objects, use \var{virtual} instead to override
% a method of a parent object
parser_e_cant_use_inittable_here=03151_E_?????? ?????? ??? ?????? ????? ?? ????? ???? ?????? ????? ??????? variant
% Some data type (e.g. \var{ansistring}) needs initialization/finalization
% code which is implicitly generated by the compiler. Such data types
% can't be used in the variant part of a record.
parser_e_resourcestring_only_sg=03152_E_?? ???? ?????? Resourcestring ???? ????? ??????, ?? ????? ??????? ?? ?????
% Resourcestring can not be declared local, only global or using the static
% directive.
parser_e_exit_with_argument_not__possible=03153_E_?????? ?????? exit ???? ???? ?????? ?????? ??????
% an exit statement with an argument for the return value can't be used here, this
% can happen e.g. in \var{try..except} or \var{try..finally} blocks
parser_e_stored_property_must_be_boolean=03154_E_????? ??????? ?????? ?????? ???? ????? ???????
% If you specify a storage symbol in a property declaration, it must be of
% the type boolean
parser_e_ill_property_storage_sym=03155_E_?????? ???? ???? ????? ?????? ??????
% You can't use this type of symbol as storage specifier in property
% declaration. You can use only methods with the result type boolean,
% boolean class fields or boolean constants
parser_e_only_publishable_classes_can_be_published=03156_E_?? ????? ??????? ???? $M+ ????? ????? ????? ? published
% In the published section of a class can be only class as fields used which
% are compiled in \var{\{\$M+\}} or which are derived from such a class. Normally
% such a class should be derived from TPersitent
parser_e_proc_directive_expected=03157_E_???? ??????? ?????
% This error is triggered when you have a \var{\{\$Calling\}} directive without
% a calling convention specified.
% It also happens when declaring a procedure in a const block and you
% used a ; after a procedure declaration which must be followed by a
% procedure directive.
% Correct declarations are:
% \begin{verbatim}
% const
%   p : procedure;stdcall=nil;
%   p : procedure stdcall=nil;
% \end{verbatim}
parser_e_invalid_property_index_value=03158_E_???? ??????? ?? ?????? ???? ????? ????? ?????
% The value you use to index a property must be of an ordinal type, for
% example an integer or enumerated type.
parser_e_procname_to_short_for_export=03159_E_?? ????? ??? ???? ??????
% The length of the procedure/function name must be a…