CLASS X: IMPLEMENTATION DEPENDENT FEATURES
ERROR MESSAGES FOR MAJOR CLASSIFICATION F
CLASSIFICATION “F” ERRORS DEAL WITH FORMAL PARAMETERS AND ARGUMENTS FD100 - SEVERITY 2
ARRAYNESS CONFLICT ON PARAMETER #??
THE NUMBER OF DIMENSIONS OF ARRAYNESS OF THE ARGUMENT AND ITS CORRESPONDING FORMAL PARAMETER DO NOT AGREE. SEE SPEC SECTIONS 6.4, 7.4.
FD101 - SEVERITY 2
SIZE CONFLICT ON VECTOR/MATRIX PARAMETER #??
ALL VECTOR/MATRIX ARGUMENTS MUST AGREE IN SIZE WITH THE FORMAL PARAMETERS THEY REPLACE. SEE SPEC-SECTIONS 6.4, 7.4
FD102 - SEVERITY 2
ARRAY SIZE CONFLICT ON PARAMETER #??
THE SIZE OF AN ARRAYNESS DIMENSION OF THE ARGUMENT AND ITS CORRESPONDING FORMAL PARAMETER DO NOT AGREE. SEE SPEC SECTIONS 6.4, 7.4.
FD103 - SEVERITY 2
STRUCTURE COPYNESS CONFLICT ON PARAMETER #??
SAME AS FD101, BUT PERTAINING TO COPYNESS
FD104 - SEVERITY 2
STRUCTURE COPY SIZE CONFLICT ON PARAMETER #??
SAME AS FD102, BUT PERTAINING TO COPYNESS
FD4 - SEVERITY 2
ARRAYNESS OF FUNCTION ARGUMENT DOES NOT MATCH CURRENT ARRAYNESS OF EXPRESSION CONTAINING THE INVOCATION
IF AN ARRAY IS PASSED AS AN ARGUMENT TO A FUNCTION WHICH HAS A SINGLE VALUED PARAMETER, THE FUNCTION WILL BE REPETITIVELY INVOKED FOR EACH ARRAY ELEMENT TO CREATE A SIMILARLY ARRAYED RETURN VALUE. SUCH AN ARRAY MUST BE LEGAL WITHIN THE EXPRESSION IN WHICH THE FUNCTION CALL IS FOUND. SEE SPEC-SECTION 6.4
FD6 - SEVERITY 2
ARGUMENT OF ?? FUNCTION IS NOT A SQUARE MATRIX
DET, INVERSE, AND TRACE MAY ONLY BE USED ON SQUARE MATRICES. SPEC-APPENDIX C
FD7 - SEVERITY 2
A NAME PSEUDO-FUNCTION MAY NOT POSSESS MULTIPLE COPIES IF AN ARGUMENT OF A PROCEDURE CALL.
FN100 - SEVERITY 2
WRONG NUMBER OF PERCENT MACRO ARGUMENTS
SVC EXPECTS 1 ARGUMENT, NAMECOPY 2 ARGUMENTS, COPY 2 OR 3, NAMEBIAS 2 ARGUMENTS, AND NAMEADD 3 ARGUMENTS. SEE USER’S GUIDE-SECTION 8.7
FN102 - SEVERITY 2
INCORRECT NUMBER OF ARGUMENTS TO ??
EXAMPLE:
CALL ABC(X,Y,Z); ABC:PROCEDURE(X,Y);
INVOKING ABC SPECIFIES 3 PARAMETERS, BUT THE PROCEDURE DECLARATION CONTAINS 2 ARGUMENTS.
HAL/S-FC User’s Manual USA003090 32.0/17.0
B -38 November 2005
UNEXPECTED PERCENT MACRO ARGUMENT FN105 - SEVERITY 1
?? OF %COPY INVOLVES A NAME VARIABLE DEREFERENCE. NOT CHECKED. FN106 - SEVERITY 2
ELEMENT BOUNDARY EXCEEDED FOR ?? OF %COPY FN107 - SEVERITY 1
?? OF %COPY INVOLVES RUNTIME ADDRESSING. NOT CHECKED. FN108 - SEVERITY 1
?? OF %COPY INVOLVES A PASS-BY-REFERENCE PARAMETER DEREFERENCE. NOT CHECKED.
FN3 - SEVERITY 3
?? USED MORE THAN ONCE AS A PARAMETER
EACH FORMAL PARAMETER MUST BE UNIQUELY NAMED.
FN4 - SEVERITY 2
?? FUNCTION HAS INCORRECT NUMBER OF ARGUMENTS
THIS IS THE RESULT OF CALLING A HAL/S BUILT-IN FUNCTION WITH AN INCORRECT NUMBER OF ARGUMENTS.
FS1 - SEVERITY 2
AN ASSIGN ARGUMENT OF A PROCEDURE CALL MAY NOT BE A SUBBIT PSEUDO VARIABLE
SEE SPEC-SECTION 6.5.4
FS2 - SEVERITY 2
THE STRUCTURE COPIES OF ASSIGN ARGUMENT ?? MUST BE SUBSCRIPTED AWAY
SEE SPEC-SECTION 7.4
FT10 - SEVERITY 2
A NAME PSEUDO-FUNCTION MAY NOT BE THE ARGUMENT OF A BUILT-IN OR SHAPING/CONVERSION FUNCTION.
FT100 - SEVERITY 2
ILLEGAL ARGUMENT TO SIZE FUNCTION
THE ARGUMENT TO THE BUILT-IN SIZE FUNCTION MUST BE AN UNSUBSCRIPTED DATA ITEM WITH A ONE DIMENSIONAL ARRAY SPECIFICATION OR A MULTIPLE COPY SPECIFICATION, OR ELSE AN UNSUBSCRIPTED BUT (ONE DIMENSIONALLY) ARRAYED STRUCTURE TERMINAL. SPEC-APPENDIX C
FT101 - SEVERITY 2
DATA TYPE CONFLICT ON PARAMETER #??
DATA TYPE IN PARAMETER AND ARGUMENT MUST BE COMPATIBLE. SEE SPEC-SECTIONS 6.4, 7.4, 11.4.9
FT102 - SEVERITY 2
ASSIGN PARAMETER ATTRIBUTES MUST MATCH
THE ATTRIBUTES OF A PROCEDURE’S ASSIGN PARAMETERS MUST MATCH PRECISELY THE ATTRIBUTES OF THE ARGUMENTS EMPLOYED WHEN THE PROCEDURE IS CALLED: THIS IS TRUE OF TYPE, PRECISION, DIMENSION, ARRAYNESS, AND STRUCTURE TREE ORGANIZATION. THE REMOTE ATTRIBUTE MUST ALSO MATCH IF THE ASSIGN PARAMETER IS NON-REMOTE OR IS A NAME VARIABLE. CHARACTER LENGTHS NEED NOT MATCH PRECISELY, HOWEVER. SPEC- SECTION 7.4
FT103 - SEVERITY 2
LOCK NUMBER CONFLICT ON PARAMETER #??
IF AN ASSIGN ARGUMENT IN A PROCEDURE CALL IS OF LOCK GROUP N, THEN THE
CORRESPONDING ASSIGN PARAMETER MUST ALSO BE OF LOCK GROUP N, OR ELSE OF (*). IF THE ASSIGN ARGUMENT IS OF GROUP (*), THE ASSIGN PARAMETER MUST BE TOO. SPEC- SECTION 7.4
FT104 - SEVERITY 2
ILLEGAL NAME PARAMETER #??
THE ARGUMENT OF A NAME PSEUDO-FUNCTION WHICH IS A PARAMETER MUST BE EITHER NULL OR A VARIABLE. EXPRESSIONS ARE NOT ALLOWED.
FT105 - SEVERITY 2
NOT ASSIGN PARAMETER
ALL ARGUMENTS IN A PROCEDURE CALL WHICH ARE USED AS ASSIGN ARGUMENTS MUST CORRESPOND TO A DEFINED ASSIGN PARAMETER IN THE PROCEDURE DEFINITION. FOR EXAMPLE:
PROC1:PROCEDURE ASSIGN(A,B,C); CALL PROC1(A,B,C);
OR
PROC1:PROCEDURE(A,B) ASSIGN(C); CALL PROC1(A) ASSIGN(B,C);
FT106 - SEVERITY 2
NOT NAME PARAMETER
IF AN ARGUMENT OF A PROCEDURE OR FUNCTION IS A NAME VALUE, THE CORRESPONDING FORMAL PARAMETER OF THE PROCEDURE OR FUNCTION MUST BE DECLARED AS HAVING THE NAME ATTRIBUTE AS WELL.
FT107 - SEVERITY 2
INVALID ARGUMENT TO ARRAY FUNCTION
MAX, MIN, PROD, AND SUM ALL REQUIRE THEIR ARGUMENTS TO BE ARRAYS OF INTEGERS OR SCALARS. SEE SPEC-APPENDIX C
FT108 - SEVERITY 2
ATTEMPT TO PASS REMOTE PARAMETER BY REFERENCE TO RTL ROUTINE THAT DOES NOT SUPPORT REMOTE ADDRESSING
FT109 - SEVERITY 2
ASSIGN PARAMETER MUST NOT HAVE DENSE ATTRIBUTE
THIS MESSAGE APPLIES TO BIT STRUCTURE NODES.
FT110 - SEVERITY 2
MISMATCHED ARGUMENTS IN %NAMEADD STATEMENT. REMOTE SOURCE NOT ALLOWED WITH NON-REMOTE DESTINATION IN %NAMEADD STATEMENT. FT111 - SEVERITY 2
MISMATCHED ARGUMENTS IN %NAMECOPY STATEMENT. REMOTE SOURCE NOT ALLOWED WITH NON-REMOTE DESTINATION IN %NAMECOPY STATEMENT.
FT112 - SEVERITY 2
PARAMETER #?? MAY NOT BE NAME (NAMEVAR) IF NAMEVAR LIVES REMOTE
THE REMOTE KEYWORD ON A NAME VARIABLE SPECIFIES WHERE IT POINTS, NOT WHERE IT LIVES. THERE IS NO CURRENT WAY TO DECLARE A REMOTE NAME INSIDE A
HAL/S-FC User’s Manual USA003090 32.0/17.0
B -40 November 2005
FT113 - SEVERITY 2
REMOTE INPUT ARGUMENT CANNOT BE PASSED INTO NON-REMOTE NAME PARAMETER.
FT2 - SEVERITY 2
?? FUNCTION HAS AN ARGUMENT OF INCORRECT TYPE
SEE SPEC, APPENDIX C, FOR COMPLETE INFORMATION ON THE TYPE OF ARGUMENTS USED IN BUILT-IN FUNCTIONS.
FT3 - SEVERITY 2
ILLEGAL TYPE FOR THE FUNCTION ??
FUNCTIONS MAY NOT BE EVENT TYPE.
FT4 - SEVERITY 2
THE SIZE SPECIFICATION FOR THE RETURN TYPE OF FUNCTION ?? DISAGREES WITH THE PREVIOUSLY DECLARED SIZE
THE SPECIFICATION OF THE DIMENSIONALITY OF THE VALUE RETURNED BY A FUNCTION HEADER MUST MATCH THAT OF ANY EARLIER DECLARE STATEMENT IN WHICH THE FUNCTION WAS FIRST MENTIONED.
FT6 - SEVERITY 2
THE STRUCTURE TEMPLATE INDICATED IN THE TYPE SPECIFICATION OF FUNCTION ?? DISAGREES WITH THE TEMPLATE USED IN A PREVIOUS DECLARATION
THE SPECIFICATION OF THE ORGANIZATION OF THE STRUCTURE RETURNED BY A FUNCTION IN THE ACTUAL FUNCTION HEADER MUST MATCH THAT OF ANY EARLIER DECLARE STATEMENT IN WHICH THE FUNCTION WAS FIRST MENTIONED
FT7 - SEVERITY 2
CONFLICTING SINGLE/DOUBLE SPECIFICATION FOR THE FUNCTION ??
THE SPECIFICATION OF THE PRECISION OF THE VALUE RETURNED BY A FUNCTION IN THE ACTUAL FUNCTION HEADER MUST MATCH THAT OF ANY EARLIER DECLARE STATEMENT IN WHICH THE FUNCTION WAS FIRST MENTIONED.
FT8 - SEVERITY 2
THE FUNCTION ?? MAY POSSESS NEITHER A SUBSCRIPT NOR A PRECISION QUALIFIER. F100 - SEVERITY 2
ASSIGN PARAMETER NOT SYMBOL
ASSIGN PARAMETER CAN ONLY BE A VARIABLE, EXPRESSIONS ARE NOT ALLOWED.
F101 - SEVERITY 2
PERCENT MACRO CALL CONFLICT F102 - SEVERITY 2
NESTED PERCENT MACRO
%MACROS MAY NOT BE NESTED WITHIN EACH OTHER
F103 – SEVERITY 2
THE LITERAL VALUE FOR THE SHIFT COUNT IS OUT OF RANGE.