Messages

Ada-ASSURED reports three kinds of standards enforcement message:

• --ERROR--,
• --VIOLATION--, and
• --INDICATOR--.

• Ada 83 LRM refers to the Annotated Ada Reference Manual, 2nd Edition.
• Ada 95 LRM refers to the Ada 95 Reference Manual.
• Ada LRM refers to both of the above.
• AQ&S refers to the Ada Quality and Style guidelines published by the Software Productivity Consortium.

The text of the diagnostic messages can be customized by using the scripting language function sg:change-diagnostic-message!.

ERROR Messages

• [E1] This is not a valid function designator.

  Syntactic categories: name_start.

  Reference: Ada LRM 4.5.

  The user has attempted to use a non-valid string literal as a function designator. Valid function designators are listed in Section 4.5 of the Ada LRM.

• [E2] Cannot initialize a parameter specification in this mode.

  Syntactic categories: parameter_specification.

  Reference: Ada LRM 6.1.

  A parameter with an optional initialization clause can only be an in parameter. Any other mode will cause this error message.

• [E3] Statement_list cannot be empty here.

  Syntactic categories: statement_list.

  Reference: Ada LRM 5.

  This message appears if a statement list contains no valid statements. For example, if all the lines in the statement list are comments.

• [E4] Statement_list cannot consist solely of pragmas.

  Syntactic categories: statement_list.

  Reference: Ada LRM 5.

  This message appears if all the lines in the statement list are pragmas.

• [E5] This declaration must precede all bodies.

  Syntactic categories: declaration_list.

  Reference: Ada LRM 3.9.

  An attempt has been made to put a representation clause, object declaration, type declaration, exception declaration, or renaming declaration after a subprogram body. Note, this error only applies to the Ada 83 product; the restriction has been removed in Ada 95.

• [E6] All entries must precede representation clause occurrence.

  Syntactic categories: is_entry_list.

  Reference: Ada LRM 9.1.

  In a task specification, the user has put an entry declaration after a representation clause. Note, this error only applies to the Ada 83 product; the restriction has been removed in Ada 95.

• [E7] A formal part is not legal here.

  Syntactic categories: generic_instantiation.

  Reference: Ada LRM 12.1.

  The user has put a formal part in a generic instantiation.

• [E8] Unused message number.

• [E9] An association cannot be a character literal.

  Syntactic categories: association_list.

  Reference: Ada LRM 2.8, 6.4.

  A character literal has been used as an association name. For example, pragma Foo('a' => x);

• [E10] Positional association is only legal before named association
  occurs. Click HERE for transform.

  Syntactic categories: association, component_association.

  Reference: Ada LRM 2.8, 4.3 and 6.4.

  A positional association item has occurred after a named association.

• [E11] An association can only be a single identifier or operator symbol.

  Syntactic categories: association, component_association.

  Reference: Ada LRM 2.8, 4.3 and 6.4.

  A qualified name has been used as an association name. For example, pragma Foo(a.b => x);

• [E12] A qualified expression must have its expression or aggregate last.

  Syntactic categories: name.

  Reference: Ada LRM 4.7.

  Self explanatory. For example, it appears in the following expression:
  A'(X => Y).Z

• [E13] A single element aggregate must use named notation.

  Syntactic categories: aggregate.

  Reference: Ada LRM 4.3.

  Self explanatory. For example, it appears in the following enumeration representation clause: for x use (a);

• [E14] Cannot mix discrete ranges with associations in a constraint.

  Syntactic categories: aggregate.

  Reference: Ada LRM 4.3.

  Self explanatory. For example, it appears in the following declaration:
  A : X (Y, 1..2);

• [E15] A discrete range is not allowed here.

  Syntactic categories: aggregate.

  Reference: Ada LRM 4.3.

  This message appears when a range appears in an illegal context. For example, in the following procedure call: P(1 .. 2);

• [E16] Only one discrete range is allowed in a slice.

  Syntactic categories: aggregate.

  Reference: Ada LRM 4.1.2.

  An aggregate in the context of a slice has more than one discrete range. For example, in the following expression: X(1 .. 2, 3 .. 4).P

• [E17] A discrete range is allowed only in a slice.

  Syntactic categories: aggregate.

  Reference: Ada LRM 4.3.

  An aggregate in the context of a slice has a component that is not a slice. For example, in the following expression: X(1 .. 2, Y).P

• [E18] Only one choice is allowed here.

  Syntactic categories: component_association, choice_list.

  Reference: Ada LRM 4.3 and 6.4.

  A component in a named association has more than one choice on the left hand side of the =>. For example, in the following statement: P(A | B => C);

• [E19] Only simple_name choices are allowed here.

  Syntactic categories: component_association, choice_list.

  Reference: Ada LRM 4.3 and 6.4.

  A component has a non-simple name, such as a slice as a choice on the left hand side of the =>. For example, in the following statement: P(1 .. 2 => A);

• [E20] A base value must be greater than or equal to one, and less than or
  equal to sixteen.

  Syntactic categories: expression.

  Reference: Ada LRM 2.4.2.

  In a based literal, the base value is outside the range 2 through 16. For example, in the following expression:

  	19#1_234#
  	

• [E21] All digits in the mantissa must be less than the base.

  Syntactic categories: expression.

  Reference: Ada LRM 2.4.2.

  In a based literal, there are digits in the mantissa that are invalid for the base. For example, in the following expression:

  	2#10_2010#
  	

• [E22] Component_list can not be empty here.

  Syntactic categories: component_list.

  Reference: Ada83 LRM 3.7. Ada95 LRM 3.8.

  A component list must include at least one real component. This message appears when there are none. For example, in the following record declaration:

  	type R is
  	   record
  	      -- one two
  	   end record;
  	

• [E23] Component_list can not consist solely of pragmas.

  Syntactic categories: component_list.

  Reference: Ada83 LRM 3.7, Ada95 LRM 3.8.

  A component list must include at least one real component. This message appears when there only pragmas in the list. For example, in the following record declaration:

  	type R is
  	    record
  	       pragma Q;
  	    end record;
  	

• [E24] A range can not be an expression.

  Syntactic categories: range.

  Reference: Ada LRM 3.5.

  This message is self explanatory. For example, it will appear for the following expression: 1 in 2

• [E25] A type_mark is not allowed here - name must be an attribute.

  Syntactic categories: range, range_constraint, component_clause.

  Reference: Ada95 LRM 3.5.

  A range in a range_constraint or a component_clause may not be a simple name. This message appears if so. For example: type F is delta Y range R;

• [E26] A qualified expression is not allowed here.

  Syntactic categories: optional_is_name, length_clause, component_clause, type_mark, range, statement (assignment), renaming_declaration, entry_call.

  Reference: Ada LRM 4.1.

  A name in any of the above categories must not be a qualified expression. If a qualified expression is detected, this message will appear. For example, in the following assignment statement: A'(B) := X;

• [E27] An attribute is required here.

  Syntactic categories: length_clause, representation_clause.

  Reference: Ada83 LRM 13.2, Ada95 LRM 13.3.

  An invalid name has been used in a representation length-clause. The name must be an attribute. For example: for X use Y;

• [E28] Name must be a simple name or operator symbol.

  Syntactic categories: association.

  Reference: Ada83 LRM 2.8, 3.7, 4.3, 5.4, 6.4, 9.7.1, 11.2, and 12.3;

  Ada95 LRM 3.8.

  A name in an association must not be an attribute or a qualified expression. This message appears if so. For example: pragma P(A'B => X);

• [E29] This is not a qualified expression as originally specified—you may
  want to convert it to a subtype_indication.

  Syntactic categories: allocator.

  Reference: Ada LRM 4.8.

  Structural cutting and pasting can result in what was parsed as a name in the context of a qualified expression. Text-capturing and re-parsing the name, or invoking the transformation convert-to-subtype will correct the problem.

• [E30] Parameter specification list cannot be empty here.

  Syntactic categories: parameter_specification_list

  Reference: Ada95 LRM 6.1.

  This message appears if the parameter specification list consists solely of comments and blank lines. For example:

  	procedure P (--one
  	    );
  	

• [E31] Enumeration literal list cannot be empty here.

  Syntactic categories: enumeration_literal_specification_list.

  Reference: Ada LRM 3.5.1.

  This message appears if the enumeration specification list consists solely of comments and blank lines. For example:

  	type X is (--one
  	    );
  	

• [E32] Identifier list cannot be empty here.

  Syntactic categories: identifier_list.

  Reference: Ada83 LRM 3.2, 3.7 3.7.1, 6.1, 7.4, 11.1, and 12.1. Ada95 LRM 3.3.1, 3.3.2, 3.7, 3.8, 6.1, 11.1, and 12.4.

  This message appears if the identifier list consists solely of comments and blank lines. For example:

  	procedure P
  	    (--one
  	       : in Y);
  	

• [E33] Component association list cannot be empty here.

  Syntactic categories: component_association_list.

  Reference: Ada LRM 4.3.

  This message appears if the component association list consists solely of comments and blank lines. For example, in the following statement:

  	P(--one
  	    );
  	

• [E34] Freeform text contains syntax error.

  Syntactic categories: compilation_unit_list, context_clause_list, exception_handler_list, generic_formal_part, optional_component_clause_list, association_list,
  pragma_choice_list, component_list, basic_declaration_list, component_association_list, statement_list, parameter_specification_list, is_entry_list, protected_operation_item_list (Ada95 only).

  Reference: N/A.

  This message appears if the text bracketed by freeform-text comments cannot be parsed.

• [E35] Protected body cannot be empty here.

  Syntactic categories: protected_body (Ada95 only).

  Reference: Ada95 LRM 9.4.

  The protected operation item list consists solely of comments and blank lines.

• [E36] Syntax error in file.

  A syntax error was found somewhere in the text of the file. Further analysis of the contents is not possible until this has been corrected.

• [V0] The identifier/keyword <id> is used in context <context>.

  Syntactic categories: name, identifier.

  Enforcement parameters:
  Violations For Selected Identifiers,
  Identifiers To Be Flagged As Violations.

  Reference: AQ&S 3.1.4, 5.9.1, 5.9.2, 5.9.7, 6.2.2, 6.2.3, 7.2.1, 7.4.3, 7.5.2, 7.5.3, 7.6.2, 7.6.4, 7.6.5, 7.6.7, 7.6.6, 7.7.1, 7.7.4, 8.4.2.

  If Violations For Selected Identifiers is on and if identifier <id> appears in context <context>, then this message will appear.

• [V1] A list with this many items must be a named association list. Click
  HERE for transform.

  Syntactic categories: component_association_list, association_list.

  Enforcement parameters:
  Named Association For Instantiations,
  Named Association For Names,
  Named Association For Aggregates,
  Named Association For Pragmas.

  Reference: AQ&S 5.2.2, 5.6.10.

  If any of the items in the list use positional notation, and the number of items in the list exceeds the parameter appropriate for the context in which the list is found, then this message is printed. Clicking on the message enables the transformation convert-list-to-named.

• [V2] Only named associations are allowed here. Click HERE for transform.

  Syntactic categories: generic_instantiation, association.

  Enforcement parameters:
  Named Association For Instantiations,
  Named Association For Names,
  Named Association For Aggregates,
  Named Association For Pragmas.

  Reference: AQ&S 5.2.2, 5.6.10.

  If the named association threshold is one, and there is only one item in the list, this message is printed rather than violation message V1.

• [V3] A trailing (righthand) comment must be present here.

  Syntactic categories: statement (if, case), optional_else.

  Enforcement parameters:
  Marker Comment Loc,
  Marker Comment Nest Level,
  Else Marker Comment Loc,
  Else Marker Comment Nest Level.

  Reference: AQ&S 3.3.7.

  If statements and case statements consisting of more than Marker Comment Loc lines of code (loc) or more than Marker Comment Nest Level nesting levels of code require a marker comment on their end if or end case. If statements consisting of more than Else Marker Comment Loc lines of code (loc) or more than Else Marker Comment Nest Level nesting levels require a marker comment on their else.

• [V4] Use of GOTO is not allowed.

  Syntactic categories: statement.

  Enforcement parameters: Goto enforcement.

  Reference: AQ&S 5.6.7.

  If the enforcement parameter is on, then this message appears for every occurrence of a goto statement.

• [V5] Labels are not %allowed since GOTO is not allowed.

  Syntactic categories: statement.

  Enforcement parameters: Goto enforcement.

  Reference: AQ&S 5.6.7.

  If the enforcement parameter is on, then this message appears for every occurrence of a statement that has a label.

• [V6] Must have an OTHERS exception handler here.

  Syntactic categories: task_body.

  Enforcement parameters: Others Handlers in Tasks Enforcement.

  Reference: AQ&S 6.3.4.

  If the enforcement parameter is on, then this message appears when a task body does not have an others exception handler present.

• [V7] Nested loops must ALL be named.

  Syntactic categories: statement (loop).

  Enforcement parameters: Nested Loop Naming Enforcement.

  Reference: AQ&S 5.1.1, 5.1.3.

  If the enforcement parameter is on, then all nested loops must be named. This message will appear for each occurrence of a nested loop.

• [V8] Exit statements from named loops must be named.

  Syntactic categories: statement (exit).

  Enforcement parameters: Nested Loop Naming Enforcement.

  Reference: AQ&S 5.1.1, 5.1.3.

  If the enforcement parameter is on, then if a loop is required to be named, then any exit statements within the loop must also be named.

• [V9] Only one identifier is allowed per clause. Click HERE for
  transform.

  Syntactic categories: with_clause, component_declaration, object_declaration (objects, constants, numbers) discriminant_specification, declaration (exceptions), parameter_specification, use_clause.

  Enforcement parameters: Single Identifier List Enforcement.

  Reference: none.

  If the enforcement parameter is on, then identifier lists in each of the above syntactic categories must contain no more than one identifier per clause. Clicking on the message will enable the transformation convert-to-singleton which can be used to correct the violation.

• [V10] All BLOCKS must be named.

  Syntactic categories: statement (block).

  Enforcement parameters: Block Naming Enforcement.

  Reference: AQ&S 5.1.2.

  If the enforcement parameter is on, then this message will appear for all blocks that are unnamed.

• [V11] Anonymous tasks are not allowed. Click HERE for type insertion
  transform.

  Syntactic categories: task_specification.

  Enforcement parameters: Anonymous Task Type Enforcement.

  Reference: AQ&S 6.1.3.

  If the enforcement parameter is on, then anonymous tasks are disallowed. Clicking on the message enables the transformation insert-type which can be used to correct the violation.

• [V12] Non-constant object declarations are not permitted in the visible
  part of a package specification.

  Syntactic categories: package_declaration, declaration (object, array).

  Enforcement parameters: Exported Variable Enforcement.

  Reference: AQ&S 4.1.7.

  If the enforcement parameter is on, then this message will appear for all variable declarations in the visible part of a package specification. For example:

  	package P is
              --VIOLATION-- Non-constant object declarations are
              --VIOLATION--   not permitted in the visible part of
              --VIOLATION--   a package specification.
  	    A : B;
  	end P;
  	

• [V13] Anonymous type declarations are not allowed.

  Syntactic categories: optional_constraint, declaration (array, constant array).

  Enforcement parameters: Anonymous Type Enforcement.

  Reference: AQ&S 5.3.2.

  If the enforcement parameter is on, then this message appears for all occurrences of anonymous types. An anonymous type is defined as an inline declaration of an array.

• [V14] The following list is not ordered. Click HERE for transform when
  finished.

  Syntactic categories: parameter_specification_list.

  Enforcement parameters: Parameter Order Enforcement.

  Reference: AQ&S 5.2.3.

  If the enforcement parameter is on, then parameter specifications are required to be sorted by mode. The required order is in, in out, out and finally in parameters with default values.

• [V15] Statement nesting depth of <n> exceeds maximum of <m>.

  Syntactic categories: subprogram_body, package_body, task_body

  Enforcement parameters: Control Nesting Depth.

  Reference: AQ&S 5.6.1.

  This message appears for every body that has a nesting depth greater than the value of the enforcement parameter. The nesting depth of a body is defined as the maximum nest level of any statement or optional exception part in the body, where the nest level of a statement is defined recursively as follows: If the statement encloses another statement_list, then the nest level of the statement is 1 + the maximum nest level of any enclosed statement. Otherwise, the nest level is zero. The nest level of an optional exception part is 1 + the maximum nest level of any enclosed statement.

• [V16] Expression nesting depth of <n> exceeds maximum of <m>.

  Syntactic categories: expression.

  Enforcement parameters: Expression Nesting Depth.

  Reference: AQ&S 5.6.1.

  This message appears for every top level expression that has a nesting depth greater than the enforcement parameter. The nesting depth of an expression, where that expression is an arithmetic or logical expression, is defined as the maximum nest level of any subexpression contained within the expression. The nest level of an expression is defined recursively as follows: If the expression has no subexpression, its nest level is zero. Otherwise, if the precedence of the expression is not equal to the precedence of any of its subexpressions, then its nest level is 1 + the maximum nest level of all of its subexpressions.

• [V17] Subprogram body size of <n> exceeds maximum of <m>.

  Syntactic categories: subprogram_body.

  Enforcement parameters: Subprogram Body Size.

  Reference: none.

  This message appears for every subprogram body whose body size exceeds the value of the enforcement parameter. Sizes are measured in terms of lines of code. The size of a subprogram body is defined as: the size of the header and parameter specification part + the size of the declaration part + the size of the begin-end part.

• [V18] Task body size of <n> exceeds maximum of <m>.

  Syntactic categories: task_body.

  Enforcement parameters: Task Body Size.

  Reference: none.

  This message appears for every task body whose body size exceeds the value of the enforcement parameter. Sizes are measured in terms of lines of code. The size of a subprogram body is defined as: 1 + the size of the declaration part + the size of the begin-end part.

• [V19] Number of negative logic occurrences of <n> exceeds maximum of <m>.

  Syntactic categories: expression.

  Enforcement parameters: Negative Logic Occurrences.

  Reference: AQ&S 5.5.4.

  This message appears for every top level expression whose negative logic exceeds the enforcement parameter. The negative logic of an expression is recursively defined as follows: The negative logic of a not or not in expression is 1 + the negative logic of its subexpression. The negative logic of any other expression is the maximum of the negative logic of all its subexpressions.

• [V20] Task specifications are not allowed in the visible part of a package
  specification.

  Syntactic categories: task_declaration.

  Enforcement parameters: Exported Task Enforcement.

  Reference: AQ&S 4.2.4.

  This message is self-explanatory.

• [V22] Above item must be initialized if it is to remain in its current
  position.

  Syntactic categories: parameter_specification_list.

  Enforcement parameters: Parameter Order Enforcement.

  Reference: AQ&S 5.2.3.

  If the enforcement parameter is on, this message appears if the parameter specification list contains in parameters without default expressions occurring after in parameters with default expressions.

• [V23] File contains more than one compilation unit.

  Syntactic categories: compilation_unit_list.

  Enforcement parameters: Separate Compilation Unit Enforcement.

  Reference: AQ&S 4.1.1.

  If the enforcement parameter is on, this message appears when more than one compilation unit occurs in a buffer.

• [V24] An identifier list must not have interleaved comments here.

  Syntactic categories: identifier list.

  Enforcement parameters: Commented Identifier Enforcement.

  Reference: none.

  If the enforcement parameter is on, this message appears when an identifier list has interleaved comments.

• [V25] A loop this long must be named.

  Syntactic categories: statement (loop).

  Enforcement parameters: Unnamed Loops.

  Reference: none.

  This message appears for every occurrence of a loop whose size exceeds the value of the enforcement parameter.

• [V26] Use of ABORT is not allowed.

  Syntactic categories: statement (abort).

  Enforcement parameters: Abort Enforcement.

  Reference: AQ&S 6.3.3.

  If the enforcement parameter is on, then this message appears for every occurrence of an abort statement.

• [V27] Derived types are not allowed.

  Syntactic categories: type_declaration.

  Enforcement parameters: Derived Type Enforcement.

  Reference: none.

  If the enforcement parameter is on, then this message appears for every occurrence of a derived type.

• [V28] Access types are not allowed.

  Syntactic categories: type_declaration.

  Enforcement parameters: Access Type Enforcement.

  Reference: none.

  If the enforcement parameter is on, then this message appears for every occurrence of an access type.

• [V34] Freeform text is not allowed.

  Syntactic categories: All.

  Enforcement parameters: Freeform Text Enforcement.

  Reference: none.

  This message appears if there is a use of freeform-text comments to escape from formatting.

• [V35] Protected specifications are not allowed in the visible part of a
  package specification.

  Syntactic categories: protected_definition.

  Enforcement parameters: Exported Protected Enforcement.

  Reference: AQ&S 5.3.3.

  This message is self-explanatory.

• [V36] Protected type specifications are not allowed in the visible part of
  a package specification.

  Syntactic categories: type_definition (protected type).

  Enforcement parameters: Exported Protected Type Enforcement.

  Reference: AQ&S 6.1.2.

  This message is self-explanatory.

• [V37] Aliased objects are not allowed.

  Syntactic categories: object_declaration, type_definition (constrained array).

  Enforcement parameters: Aliased Object Enforcement.

  Reference: AQ&S 5.4.4.

  If the enforcement parameter is on, then this message appears for every occurrence of an aliased object.

• [I0] The identifier <id> is used in context <context>.

  Syntactic categories: name, identifier.

  Enforcement parameters: Indicators For Selected Identifiers.

  Reference: AQ&S 3.1.4, 5.9.1, 5.9.2, 5.9.7, 6.2.2, 6.2.3, 7.2.1, 7.4.3, 7.5.2, 7.5.3, 7.6.2, 7.6.4, 7.6.5, 7.6.7, 7.6.6, 7.7.1, 7.7.4, 8.4.2.

  If Indicators For Selected Identifiers is on and if identifier <id> appears in context <context>, then this message will appear.

• [I1] Number of negative logic occurrences exceeds recommended maximum.

  Syntactic categories: expression.

  Enforcement parameters: Negative Logic Occurrences.

  Reference: AQ&S 5.5.4.

  This is the indicator form of violation V19.

• [I2] Expression nesting depth exceeds recommended maximum.

  Syntactic categories: expression.

  Enforcement parameters: Expression Nesting Depth.

  Reference: AQ&S 5.6.1.

  This is the indicator form of violation V16.

• [I3] Statement nesting depth exceeds recommended maximum.

  Syntactic categories: subprogram_body, package_body, task_body.

  Enforcement parameters: Control Nesting Depth.

  Reference: AQ&S 5.6.1.

  This is the indicator form of violation V15.

• [I4] Task Body exceeds recommended size limit.

  Syntactic categories: task_body.

  Enforcement parameters: Task Body Size.

  Reference: none.

  This is the indicator form of violation V18.

• [I5] Subprogram Body exceeds recommended size limit.

  Syntactic categories: subprogram_body.

  Enforcement parameters: Subprogram Body Size.

  Reference: none.

  This is the indicator form of violation V17.

• [I6] Code statement present in Subprogram Body.

  Syntactic categories: subprogram_body.

  Enforcement parameters: Indicators For Code Statements.

  Reference: AQ&S 7.6.3.

  If the enforcement parameter is on, then the message appears if a code statement exists in the subprogram body.

• [I7] Code statement present in Package Body.

  Syntactic categories: package_body.

  Enforcement parameters: Indicators For Code Statements.

  Reference: AQ&S 7.6.3.

  If the enforcement parameter is on, then the message appears if a code statement exists in the package body.

• [I8] Code statement present in Task Body.

  Syntactic categories: task_body.

  Enforcement parameters: Indicators For Code Statements.

  Reference: AQ&S 7.6.3.

  If the enforcement parameter is on, then the message appears if a code statement exist in the task body.

• [I9] Others exception handler present.

  Syntactic categories: exception_handler_list.

  Enforcement parameters: Indicators For Others Handlers.

  Reference: AQ&S 5.8.2.

  If the enforcement parameter is on, then this message occurs if an others handler is present in an exception handler list.

• [I10] Task declaration is present.

  Syntactic categories: task_specification.

  Enforcement parameters: Indicators For Tasks.

  Reference: none.

  If the enforcement parameter is on, then this message appears when a task specification occurs.

• [I11] Generic Package instantiation is present.

  Syntactic categories: generic_instantiation.

  Enforcement parameters: Indicators For Generics.

  Reference: none.

  Self explanatory.

• [I12] Generic Subprogram instantiation is present.

  Syntactic categories: generic_instantiation.

  Enforcement parameters: Indicators For Generics.

  Reference: none.

  Self explanatory.

• [I13] Not used.

• [I14] Dynamic memory allocation: Access type defined.

  Syntactic categories: type_definition, expression.

  Enforcement parameters: Indicators For Dynamic Memory.

  Reference: none.

  Appears if an access type is defined.

• [I15] Dynamic memory allocation.

  Syntactic categories: type_definition, expression.

  Enforcement parameters: Indicators For Dynamic Memory.

  Reference: none.

  Appears if an allocator occurs.

• [I16] Abort statement present.

  Syntactic categories: statement (abort).

  Enforcement parameters: Indicators For Abort Statements.

  Reference: AQ&S 6.3.3, 7.4.6.

  Self explanatory.

• [I17] Enumeration representation clause present.

  Syntactic categories: representation_clause, address_clause, length_clause.

  Enforcement parameters: Indicators For Representation Clauses.

  Reference: AQ&S 7.6.1.

  Self explanatory.

• [I18] Record representation clause present.

  Syntactic categories: representation_clause, address_clause, length_clause.

  Enforcement parameters: Indicators For Representation Clauses.

  Reference: AQ&S 7.6.1.

  Self explanatory.

• [I19] Address clause present.

  Syntactic categories: representation_clause, address_clause, length_clause.

  Enforcement parameters: Indicators For Representation Clauses.

  Reference: AQ&S 7.6.1.

  Self explanatory.

• [I20] Length clause present.

  Syntactic categories: representation_clause, address_clause, length_clause.

  Enforcement parameters: Indicators For Representation Clauses.

  Reference: AQ&S 7.6.1.

  Self explanatory.

• [I21] Pragma present.

  Syntactic categories: pragma_clause.

  Enforcement parameters: Indicators For Pragmas.

  Reference: none.

  Self explanatory

• [I22] Generic Package declaration is present.

  Syntactic categories: generic_instantiation.

  Enforcement parameters: Indicators For Generics.

  Reference: none.

  Self explanatory.

• [I23] Generic Subprogram declaration is present.

  Syntactic categories: generic_instantiation.

  Enforcement parameters: Indicators For Generics.

  Reference: none.

  Self explanatory.

• [I24] Length of unnamed association list exceeds recommended maximum.

  Syntactic categories: association_list, component_association_list.

  Enforcement parameters:
  Named Association For Instantiations,
  Named Association For Names,
  Named Association For Aggregates,
  Named Association For Pragmas.

  Reference: AQ&S 5.2.2, 5.6.10.

  This is the indicator form of violation V1.

• [I25] Length of body of unnamed loop exceeds recommended maximum.

  Syntactic categories: statement (loop).

  Enforcement parameters: Unnamed Loops.

  Reference: none.

  This is the indicator form of violation V25.

• [I26] Trailing righthand comment is recommended here.

  Syntactic categories: statement (if, case), optional_else.

  Enforcement parameters:
  Marker Comment Loc,
  Marker Comment Nest Level,
  Else Marker Comment Loc,
  Else Marker Comment Nest Level.

  Reference: AQ&S 3.3.7.

  This is the indicator form of violation V3.

• [I27] Exit statement present.

  Syntactic categories: statement (loop).

  Enforcement parameters: Unnamed Loops.

  Reference: AQ&S 5.6.4.