!editorial comment 123
!topic  Corresponding_Type_Structure seems incomplete
!reference  ASIS 95-16.8
!from  Gary Barnes  98-11-11

Imagine a private type (with or without an extension) declared by some
package specification.

Then imagine another type, a type derived from that private type but
without visiblity to the private part where the private type is
completed.

Then pass that private type definition to
Corresponding_Type_Structure.  Is this interface expected to "look
through" the private type and locate the type completion?  Or were
private types simply overlooked when the description of this interface
was written?

Corrected text:

    function Corresponding_Type_Structure
                (Type_Definition : in Asis.Type_Definition)
       return Asis.Declaration;
------------------------------------------------------------------------------
-- Type_Definition - Specifies the derived_type_definition to query
--
-- Returns the type structure from which the specified type definition has
-- been derived.  This function will recursively unwind derivations and
-- subtyping until the type_declaration derives a change of representation or
-- is no longer derived.  See Reference Manual 13.6.
--
-- Appropriate Type_Kinds:
--      A_Derived_Type_Definition
--      A_Derived_Record_Extension_Definition
--
-- Returns Declaration_Kinds:
--      An_Ordinary_Type_Declaration
--      A_Task_Type_Declaration
--      A_Protected_Type_Declaration
--      A_Formal_Type_Declaration
--      A_Private_Type_Declaration          ; Added
--      A_Private_Extension_Declaration     ; Added
------------------------------------------------------------------------------

!resolution  Accept.