From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,743cbb1eadac54f3 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: question on exceptions Date: 1996/11/08 Message-ID: #1/1 X-Deja-AN: 195463664 references: <55l00n$alv@ash.ridgecrest.ca.us> organization: New York University newsgroups: comp.lang.ada Date: 1996-11-08T00:00:00+00:00 List-Id: Bob Duff says "By the way, during the design of Ada 9X, it was suggested that we have functions for querying things like the Current_Exception_Name and Current_Exception_String. However, the design team rejected this idea for the reasons explained above -- presumably the semantics of calling these at the wrong time would be "erroneous", which is bad. My main complaint about the Ada 95 design for this stuff is that the information associated with an exception *must* be of type String. I suppose you can encode whatever information you want in a string, but not with type safety." I see no reason why these could not be functoins which can only be called within a handler, checked statically by the compiler. This is how GNAT implements the DEC Current_Exception package (which has these semantics).