* Added pure-related warning messages.

This commit is contained in:
J. Gareth "Curious Kit" Moreton 2023-07-19 21:45:03 +01:00 committed by J. Gareth "Kit" Moreton
parent 84eb9490cf
commit df73ef4f64

View File

@ -481,7 +481,7 @@ scan_e_misplaced_rtti_directive=02113_E_A The RTTI directive cannot be used here
#
# Parser
#
# 03368 is the last used one
# 03375 is the last used one
#
% \section{Parser messages}
% This section lists all parser messages. The parser takes care of the
@ -1698,6 +1698,13 @@ parser_e_coperators_off=03371_E_C styled assignment operators are turned off
parser_e_cannot_evaluate_expression_at_compile_time=03372_E_Expression cannot be evaluated at compile time
% Certain operations like the size of an object cannot be determined at compile time,
% so it cannot be e.g. part of a constant expression.
parser_n_pure_analysis_too_complex=03373_N_Analysis of pure function was too complex; this call won't be evaluated further.
% While processing a pure function, the compiler determined that it is either too complex for timely analysis or it detected that it contained an infinite loop.
% The subroutine in question is no longer considered pure from this point.
parser_w_pure_ineligible=03374_W_Subroutine "$1" is not eligible to be a pure function due to the following reason: $2
% While checking to see if the subroutine could be made a pure, a construct was found that made it ineligible and otherwise impossible for the compiler to analyse.
parser_e_pure_analysis_error=03375_E_At least $1 error(s) occurred during the purity analysis of subroutine "$2".
% While checking to see if the subroutine could be made a pure, a compiler error occurred.
%
% \end{description}
%