-- Pragma handling is isolated in a separate package
-- (logically this processing belongs in chapter 4)
-with Namet; use Namet;
-with Types; use Types;
+with Namet; use Namet;
+with Snames; use Snames;
+with Types; use Types;
package Sem_Prag is
+ -- The following table lists all the implementation-defined pragmas that
+ -- may apply to a body stub (no language defined pragmas apply). The table
+ -- should be synchronized with Aspect_On_Body_Or_Stub_OK in unit Aspects if
+ -- the pragmas below implement an aspect.
+
+ Pragma_On_Body_Or_Stub_OK : constant array (Pragma_Id) of Boolean :=
+ (Pragma_Refined_Depends => True,
+ Pragma_Refined_Global => True,
+ Pragma_Refined_Post => True,
+ Pragma_SPARK_Mode => True,
+ Pragma_Warnings => True,
+ others => False);
+
-----------------
-- Subprograms --
-----------------
procedure Analyze_Pragma (N : Node_Id);
-- Analyze procedure for pragma reference node N
- procedure Analyze_CTC_In_Decl_Part (N : Node_Id; S : Entity_Id);
- -- Special analyze routine for contract-case and test-case pragmas that
- -- appears within a declarative part where the pragma is associated with
- -- a subprogram specification. N is the pragma node, and S is the entity
- -- for the related subprogram. This procedure does a preanalysis of the
- -- expressions in the pragma as "spec expressions" (see section in Sem
- -- "Handling of Default and Per-Object Expressions...").
-
- procedure Analyze_PPC_In_Decl_Part (N : Node_Id; S : Entity_Id);
- -- Special analyze routine for precondition/postcondition pragma that
- -- appears within a declarative part where the pragma is associated
- -- with a subprogram specification. N is the pragma node, and S is the
- -- entity for the related subprogram. This procedure does a preanalysis
- -- of the expressions in the pragma as "spec expressions" (see section
- -- in Sem "Handling of Default and Per-Object Expressions...").
-
- function Check_Kind (Nam : Name_Id) return Name_Id;
- -- This function is used in connection with pragmas Assertion, Check,
- -- and assertion aspects and pragmas, to determine if Check pragmas
- -- (or corresponding assertion aspects or pragmas) are currently active
- -- as determined by the presence of -gnata on the command line (which
- -- sets the default), and the appearance of pragmas Check_Policy and
- -- Assertion_Policy as configuration pragmas either in a configuration
- -- pragma file, or at the start of the current unit, or locally given
- -- Check_Policy and Assertion_Policy pragmas that are currently active.
- --
- -- The value returned is one of the names Check, Ignore, Disable (On
- -- returns Check, and Off returns Ignore).
- --
- -- Note: for assertion kinds Pre'Class, Post'Class, Invariant'Class,
- -- and Type_Invariant'Class, the name passed is Name_uPre, Name_uPost,
- -- Name_uInvariant, or Name_uType_Invariant, which corresponds to _Pre,
- -- _Post, _Invariant, or _Type_Invariant, which are special names used
- -- in identifiers to represent these attribute references.
+ procedure Analyze_Contract_Cases_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis and expansion of delayed pragma Contract_Cases
+
+ procedure Analyze_Depends_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis of delayed pragma Depends. This routine is also
+ -- capable of performing basic analysis of pragma Refined_Depends.
+
+ procedure Analyze_Global_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis of delayed pragma Global. This routine is also
+ -- capable of performing basic analysis of pragma Refind_Global.
+
+ procedure Analyze_Initial_Condition_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis of delayed pragma Initial_Condition
+
+ procedure Analyze_Initializes_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis of delayed pragma Initializes
+
+ procedure Analyze_Pre_Post_Condition_In_Decl_Part
+ (Prag : Node_Id;
+ Subp_Id : Entity_Id);
+ -- Perform preanalysis of a [refined] precondition or postcondition that
+ -- appears on a subprogram declaration or body [stub]. Prag denotes the
+ -- pragma, Subp_Id is the entity of the related subprogram. The preanalysis
+ -- of the expression is done as "spec expression" (see section "Handling
+ -- of Default and Per-Object Expressions in Sem).
+
+ procedure Analyze_Refined_Depends_In_Decl_Part (N : Node_Id);
+ -- Preform full analysis of delayed pragma Refined_Depends. This routine
+ -- uses Analyze_Depends_In_Decl_Part as a starting point, then performs
+ -- various consistency checks between Depends and Refined_Depends.
+
+ procedure Analyze_Refined_Global_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis of delayed pragma Refined_Global. This routine
+ -- uses Analyze_Global_In_Decl_Part as a starting point, then performs
+ -- various consistency checks between Global and Refined_Global.
+
+ procedure Analyze_Refined_State_In_Decl_Part (N : Node_Id);
+ -- Perform full analysis of delayed pragma Refined_State
+
+ procedure Analyze_Test_Case_In_Decl_Part (N : Node_Id; S : Entity_Id);
+ -- Perform preanalysis of pragma Test_Case that applies to a subprogram
+ -- declaration. Parameter N denotes the pragma, S is the entity of the
+ -- related subprogram. The preanalysis of the expression is done as "spec
+ -- expression" (see section "Handling of Default and Per-Object Expressions
+ -- in Sem).
procedure Check_Applicable_Policy (N : Node_Id);
-- N is either an N_Aspect or an N_Pragma node. There are two cases. If
- -- the name of the aspect or pragma is not one of those recognized as a
- -- assertion kind by an Assertion_Kind pragma, then the call has no effect.
- -- Note that in the case of a pragma derived from an aspect, the name
- -- we use for the purpose of this procedure is the aspect name, which may
- -- be different from the pragma name (e.g. Precondition for Pre aspect).
- -- In addition, 'Class aspects are recognized (and the corresponding
- -- special names used in the processing).
+ -- the name of the aspect or pragma is not one of those recognized as
+ -- an assertion kind by an Assertion_Policy pragma, then the call has
+ -- no effect. Note that in the case of a pragma derived from an aspect,
+ -- the name we use for the purpose of this procedure is the aspect name,
+ -- which may be different from the pragma name (e.g. Precondition for
+ -- Pre aspect). In addition, 'Class aspects are recognized (and the
+ -- corresponding special names used in the processing).
--
- -- If the name is valid ASSERTION_KIND name, then the Check_Policy pragma
+ -- If the name is a valid assertion kind name, then the Check_Policy pragma
-- chain is checked for a matching entry (or for an Assertion entry which
-- matches all possibilities). If a matching entry is found then the policy
- -- is checked. If it is Off, Ignore, or Disable, then the Is_Ignored flag
- -- is set in the aspect or pragma node. Additionally for policy Disable,
- -- the Is_Disabled flag is set.
+ -- is checked. If it is On or Check, then the Is_Checked flag is set in
+ -- the aspect or pragma node. If it is Off, Ignore, or Disable, then the
+ -- Is_Ignored flag is set in the aspect or pragma node. Additionally for
+ -- policy Disable, the Is_Disabled flag is set.
--
-- If no matching Check_Policy pragma is found then the effect depends on
-- whether -gnata was used, if so, then the call has no effect, otherwise
-- True have their analysis delayed until after the main program is parsed
-- and analyzed.
+ function Get_SPARK_Mode_Id (N : Node_Id) return SPARK_Mode_Id;
+ -- Given a pragma SPARK_Mode node, return the corresponding mode id
+
procedure Initialize;
-- Initializes data structures used for pragma processing. Must be called
-- before analyzing each new main source program.
+ function Is_Config_Static_String (Arg : Node_Id) return Boolean;
+ -- This is called for a configuration pragma that requires either string
+ -- literal or a concatenation of string literals. We cannot use normal
+ -- static string processing because it is too early in the case of the
+ -- pragma appearing in a configuration pragmas file. If Arg is of an
+ -- appropriate form, then this call obtains the string (doing any necessary
+ -- concatenations) and places it in Name_Buffer, setting Name_Len to its
+ -- length, and then returns True. If it is not of the correct form, then an
+ -- appropriate error message is posted, and False is returned.
+
+ function Is_Elaboration_SPARK_Mode (N : Node_Id) return Boolean;
+ -- Determine whether pragma SPARK_Mode appears in the statement part of a
+ -- package body.
+
function Is_Non_Significant_Pragma_Reference (N : Node_Id) return Boolean;
-- The node N is a node for an entity and the issue is whether the
-- occurrence is a reference for the purposes of giving warnings about
-- False is returned, then the argument is treated as an entity reference
-- to the operator.
- function Is_Config_Static_String (Arg : Node_Id) return Boolean;
- -- This is called for a configuration pragma that requires either string
- -- literal or a concatenation of string literals. We cannot use normal
- -- static string processing because it is too early in the case of the
- -- pragma appearing in a configuration pragmas file. If Arg is of an
- -- appropriate form, then this call obtains the string (doing any necessary
- -- concatenations) and places it in Name_Buffer, setting Name_Len to its
- -- length, and then returns True. If it is not of the correct form, then an
- -- appropriate error message is posted, and False is returned.
+ function Is_Private_SPARK_Mode (N : Node_Id) return Boolean;
+ -- Determine whether pragma SPARK_Mode appears in the private part of a
+ -- package.
+
+ function Is_Valid_Assertion_Kind (Nam : Name_Id) return Boolean;
+ -- Returns True if Nam is one of the names recognized as a valid assertion
+ -- kind by the Assertion_Policy pragma. Note that the 'Class cases are
+ -- represented by the corresponding special names Name_uPre, Name_uPost,
+ -- Name_uInviarnat, and Name_uType_Invariant (_Pre, _Post, _Invariant,
+ -- and _Type_Invariant).
procedure Make_Aspect_For_PPC_In_Gen_Sub_Decl (Decl : Node_Id);
-- This routine makes aspects from precondition or postcondition pragmas
-- Suppress_All at this stage, since it can appear after the unit instead
-- of before (actually we allow it to appear anywhere).
+ procedure Relocate_Pragmas_To_Body
+ (Subp_Body : Node_Id;
+ Target_Body : Node_Id := Empty);
+ -- Resocate all pragmas that follow and apply to subprogram body Subp_Body
+ -- to its own declaration list. Candidate pragmas are classified in table
+ -- Pragma_On_Body_Or_Stub_OK. If Target_Body is set, the pragma are moved
+ -- to the declarations of Target_Body. This formal should be set when
+ -- dealing with subprogram body stubs or expression functions.
+
procedure Set_Encoded_Interface_Name (E : Entity_Id; S : Node_Id);
-- This routine is used to set an encoded interface name. The node S is an
-- N_String_Literal node for the external name to be set, and E is an
projects / gcc.git / blobdiff