return Build_Siz_Exp (First (Discrete_Choices (Comp)));
elsif Nkind (Comp) = N_Iterated_Element_Association then
- return -1; -- TBD, build expression for size of the domain
+ return -1; -- ??? build expression for size of the domain
else
return -1;
raise Program_Error;
end if;
- -- TBD: fixed point types???
- -- TBverified numeric types with a biased representation???
+ -- What about fixed point types and numeric types with a biased
+ -- representation???
end Find_Numeric_Representation;
-- A subprogram instantiation does not have an explicit
-- body. If unused, we could remove the corresponding
- -- wrapper package and its body (TBD).
+ -- wrapper package and its body.
if Present (STJ.Bod) then
Spec := Corresponding_Spec (STJ.Bod);
-- Contract_Cases, Default_Initial_Condition, Initial_Condition,
-- Loop_Invariant, Loop_Variant, Refined_Post, and Subprogram_Variant.
--
- -- TBD: it might be nice to distinguish these different kinds of assertions
+ -- It might be nice to distinguish these different kinds of assertions
-- as is done in SPARK's VC_Kind enumeration type, but any distinction
-- which isn't already present in CP's BE_Message_Subkind enumeration type
-- would require more work on the CP side.
end if;
end loop;
- -- ??? TBD: Must check that "for result type R, if the
+ -- ??? Must check that "for result type R, if the
-- function is a boundary entity for type R (see 7.3.2),
-- no type invariant applies to type R; if R has a
-- component type C, a similar rule applies to C."
-- For now we only deal with aspects that do not generate
-- subprograms, or that may mention current instances of
- -- types. These will require special handling (???TBD).
+ -- types. These will require special handling???.
when Aspect_Invariant
| Aspect_Predicate
-- to the first encountered body.
-- ??? A cleaner approach may be possible and/or this solution
- -- could be extended to general-purpose late primitives, TBD.
+ -- could be extended to general-purpose late primitives.
if Present (Ctrl_Typ) then
end if;
end if;
- -- TBD : other nonoverridable aspects.
+ -- What about other nonoverridable aspects???
end Check_Nonoverridable_Aspects;
------------------------------------
elsif Extensions_Allowed and then Is_Overloaded (Exp) then
- -- TBD: Generate better ambiguity diagnostics here.
-- It would be nice if we could generate all the right error
-- messages by calling "Resolve (Exp, Any_Type);" in the
-- same way that they are generated a few lines below by the
end;
else
- -- TBD: Implement Interval_Lists for real types
+ -- ??? Need to implement Interval_Lists for real types
return False;
end if;
Domain : constant Node_Id := Name (Parent (Ent));
begin
- -- TBD : in the full version of the construct, the
+ -- ??? In the full version of the construct, the
-- domain of iteration can be given by an expression.
if Is_Entity_Name (Domain) then
-- Returns True iff every value belonging to some interval of
-- Subset also belongs to some interval of Of_Set.
- -- TBD: When we get around to implementing "is statically compatible"
+ -- When we get around to implementing "is statically compatible"
-- correctly for real types with static predicates, we may need
-- an analogous Real_Interval_List type. Most of the language
-- rules that reference "is statically compatible" pertain to
-- Do_Accessibility_Check
-- This flag is set on N_Parameter_Specification nodes to indicate
-- that an accessibility check is required for the parameter. It is
- -- not yet decided who takes care of this check (TBD ???).
+ -- not yet decided who takes care of this check???.
-- Do_Discriminant_Check
-- This flag is set on N_Selected_Component nodes to indicate that a
-- N_Procedure_Call_Statement, N_Type_Conversion,
-- N_Simple_Return_Statement, or N_Extended_Return_Statement
-- node to indicate that the tag check can be suppressed. It is not
- -- yet decided how this flag is used (TBD ???).
+ -- yet decided how this flag is used???.
-- Elaborate_Present
-- This flag is set in the N_With_Clause node to indicate that pragma