RE: Package name

["Beard, Frank" <beardf@spawar.navy.mil>]

-----Original Message-----
From: Marin David Condic [mailto:marin.condic.auntie.spam@pacemicro.com]

> I think the idea is to have something like a pragma or attribute that lets
> you get the name of the module you are in as a string. I have frequently
> wished I could write a more general exception handler (or error handler or
> simple messages at runtime...) by having something like "Context'Image" or
> some other function that would provide the fully qualified name of the
> subprogram, package, whatever that I am currently in. Example:
>
> package body Some_Package is
>    procedure Some_Procedure is
>        ....
>        Put_Line ("Running in: " & Current_Context'Image) ;
>
> having that print:
>
> Running in: Standard.Some_Package.Some_Procedure

The Aonix ObjectAda compiler on Windows NT, returns the Package,
Procedure, and line number when Exception_Information is called.
That is, assuming you produced the executable with at least
CodeView debugging included.  If you build the executable without
any debugging, then all you get is useless addresses.

For general debugging, we had to defined our own constants.  The
PACKAGE_NAME/CLASS_NAME was defined globally in the package body,
while each procedure or function had a local constant (METHOD_NAME).
It would have been really nice to have something like Context'image,
as Marin suggests.

Frank