-- Case 3a: The aspects listed below don't correspond to
-- pragmas/attributes but do require delayed analysis.
- -- Default_Value, Default_Component_Value
+ -- Default_Value can only apply to a scalar type
+
+ when Aspect_Default_Value =>
+ if not Is_Scalar_Type (E) then
+ Error_Msg_N
+ ("aspect Default_Value must apply to a scalar_Type", N);
+ end if;
+
+ Aitem := Empty;
+
+ -- Default_Component_Value can only apply to an array type
+ -- with scalar components.
+
+ when Aspect_Default_Component_Value =>
+ if not (Is_Array_Type (E)
+ and then
+ Is_Scalar_Type (Component_Type (E)))
+ then
+ Error_Msg_N ("aspect Default_Component_Value can only "
+ & "apply to an array of scalar components", N);
+ end if;
- when Aspect_Default_Value |
- Aspect_Default_Component_Value =>
Aitem := Empty;
-- Case 3b: The aspects listed below don't correspond to
-- or precondition error).
-- We do not do this for Pre'Class, since we have to put
- -- these conditions together in a complex OR expression
+ -- these conditions together in a complex OR expression.
-- We do not do this in ASIS mode, as ASIS relies on the
-- original node representing the complete expression, when
-- Build the precondition/postcondition pragma
- -- Add note about why we do NOT need Copy_Tree here ???
+ -- Add note about why we do NOT need Copy_Tree here???
Make_Aitem_Pragma
(Pragma_Argument_Associations => New_List (
end if;
-- Make pragma expressions refer to the original aspect
- -- expressions through the Original_Node link. This is
- -- used in semantic analysis for ASIS mode, so that the
- -- original expression also gets analyzed.
+ -- expressions through the Original_Node link. This is used
+ -- in semantic analysis for ASIS mode, so that the original
+ -- expression also gets analyzed.
Comp_Expr := First (Expressions (Expr));
while Present (Comp_Expr) loop
end if;
-- In older versions of Ada the corresponding pragmas
- -- specified a Convention. In Ada 2012 the convention
- -- is specified as a separate aspect, and it is optional,
+ -- specified a Convention. In Ada 2012 the convention is
+ -- specified as a separate aspect, and it is optional,
-- given that it defaults to Convention_Ada. The code
-- that verifed that there was a matching convention
-- is now obsolete.
Pragma_Name => Nam);
end;
- -- Cases where we do not delay, includes all cases where
- -- the expression is missing other than the above cases.
+ -- Cases where we do not delay, includes all cases where the
+ -- expression is missing other than the above cases.
elsif not Delay_Required or else No (Expr) then
Make_Aitem_Pragma
End_Label => Empty));
end if;
- -- Create a pragma and put it at the start of the
- -- task definition for the task type declaration.
+ -- Create a pragma and put it at the start of the task
+ -- definition for the task type declaration.
Make_Aitem_Pragma
(Pragma_Argument_Associations => New_List (
-- In the context of a compilation unit, we directly put the
-- pragma in the Pragmas_After list of the N_Compilation_Unit_Aux
-- node (no delay is required here) except for aspects on a
- -- subprogram body (see below) and a generic package, for which
- -- we need to introduce the pragma before building the generic
- -- copy (see sem_ch12), and for package instantiations, where
- -- the library unit pragmas are better handled early.
+ -- subprogram body (see below) and a generic package, for which we
+ -- need to introduce the pragma before building the generic copy
+ -- (see sem_ch12), and for package instantiations, where the
+ -- library unit pragmas are better handled early.
if Nkind (Parent (N)) = N_Compilation_Unit
and then (Present (Aitem) or else Is_Boolean_Aspect (Aspect))
FOnly : Boolean := False;
-- Reset to True for subtype specific attribute (Alignment, Size)
- -- and for stream attributes, i.e. those cases where in the call
- -- to Rep_Item_Too_Late, FOnly is set True so that only the freezing
- -- rules are checked. Note that the case of stream attributes is not
- -- clear from the RM, but see AI95-00137. Also, the RM seems to
- -- disallow Storage_Size for derived task types, but that is also
- -- clearly unintentional.
+ -- and for stream attributes, i.e. those cases where in the call to
+ -- Rep_Item_Too_Late, FOnly is set True so that only the freezing rules
+ -- are checked. Note that the case of stream attributes is not clear
+ -- from the RM, but see AI95-00137. Also, the RM seems to disallow
+ -- Storage_Size for derived task types, but that is also clearly
+ -- unintentional.
procedure Analyze_Stream_TSS_Definition (TSS_Nam : TSS_Name_Type);
-- Common processing for 'Read, 'Write, 'Input and 'Output attribute
Typ := Etype (F);
-- If the attribute specification comes from an aspect
- -- specification for a class-wide stream, the parameter
- -- must be a class-wide type of the entity to which the
- -- aspect applies.
+ -- specification for a class-wide stream, the parameter must be
+ -- a class-wide type of the entity to which the aspect applies.
if From_Aspect_Specification (N)
and then Class_Present (Parent (N))
Typ := Etype (Subp);
end if;
- -- Verify that the prefix of the attribute and the local name
- -- for the type of the formal match.
+ -- Verify that the prefix of the attribute and the local name for
+ -- the type of the formal match.
if Base_Type (Typ) /= Base_Type (Ent)
or else Present ((Next_Formal (F)))
begin
-- The following code is a defense against recursion. Not clear that
- -- this can happen legitimately, but perhaps some error situations
- -- can cause it, and we did see this recursion during testing.
+ -- this can happen legitimately, but perhaps some error situations can
+ -- cause it, and we did see this recursion during testing.
if Analyzed (N) then
return;
return;
-- The following should not be ignored, because in the first place
- -- they are reasonably portable, and should not cause problems in
- -- compiling code from another target, and also they do affect
- -- legality, e.g. failing to provide a stream attribute for a
- -- type may make a program illegal.
+ -- they are reasonably portable, and should not cause problems
+ -- in compiling code from another target, and also they do affect
+ -- legality, e.g. failing to provide a stream attribute for a type
+ -- may make a program illegal.
when Attribute_External_Tag |
Attribute_Input |
projects / platform / upstream / linaro-gcc.git / commitdiff