Re: Structured exception information

[Georg Bauhaus <bauhaus@arcor.de>]

On Mon, 2007-01-15 at 17:19 -0500, Robert A Duff wrote:
> Georg Bauhaus <bauhaus@arcor.de> writes:
> 
...
> >    type State is tagged record
> >       info: Integer;
> >    end record;

> >
> > with Handling;  use Handling;
> > procedure foo is
> >    
> >    x: Integer;
> >    
> >    function Env return State'class is
> >    begin
> >       return State'(info => x);
> >    end Env;
> >    
> > begin
> >    if 1 > 1 then
> >       raise Constraint_Error with Env'access;
> >    end if;
> > end foo;
> 
> I'm not sure exactly what you mean by the above.  Is Handling supposed
> to be provided by the Ada implementation?

Yes, I had imagined a type somewhat like (Limited_)Controlled.
Randy has clarified IIUC.

>   Is Env'Access pointing to a
> function or the result of calling the function (allocated where?)?

More or less Env'Access should designate a "pure parameterless
projection function" e.g. from an activation record into a special
memory area used by exception handlers.
When Env'Access occurs after "with" and an exception is raised,
the projection is performed, that is, the necessary copying of
fields is performed in an implementation specific way.
The storage of the projection is typed, and access is granted in
handlers only.
Env is associated with the exception occurence (Ex_Obj'Environment?).
A call will then return a read only tagged object of the special
kind mentioned above. (Uhm, this reminds me of the composed
type in Tom Moran's example, and of stream attributes :-)

As a simpler approach, and a variation of what Maciej Sobczak has
suggested, what if
 
  raise Constraint_Error with
    (Derived_from_Exception_Controlled with A => X, ...)

will restrict X to be a name of a local object? Or more generally,
a name of an object that has already been computed?
(The type of A will have to be as visible as
Derived_from_Exception_Controlled I guess.)