Re: Destroy and Unchecked Deallocation (minor bug)

[billwolf@hubcap.clemson.edu (William Thomas Wolfe,2847,)]

From article <8812140455.AA16285@ajpo.sei.cmu.edu>, by TUFFS1@alcoa.com:
> generic
>   type Object is limited private;
>   type Name is access Object;
>   with procedure Destroy(Y: in out Object) is <>;
> procedure Deallocate(X: in out Name);
> 
> with Unchecked_Deallocation;
> procedure Deallocate(X: in out Name) is
>   procedure Clean_Up is new Unchecked_Deallocation(Object, Name);
> begin
>   Destroy(X.all);
>   Clean_Up(X);
> end Deallocate;

  Deallocate needs to be revised as follows:

     begin
        if (X /= null) then  
           Destroy (X.all);  --  avoiding a CONSTRAINT_ERROR here...
           Clean_Up (X);
        end if;
     end Deallocate;

  Also, it's probably safer to revise the spec of the ADT to read:

     type POINTER_TO_ADT is access ADT;

     procedure DESTROY (TARGETED_OBJECT : in out POINTER_TO_ADT);

        -- This procedure, unlike UNCHECKED_DEALLOCATION, will
        --   properly destroy the ADT being pointed to...

  and then hide the instantiation in the package body.  This will 
  reduce the length of the user's "with" list, and give the user 
  less opportunity to screw up the instantiation,