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,d6413a22d4aaecda X-Google-Attributes: gid103376,public From: bobduff@world.std.com (Robert A Duff) Subject: Re: Program identification Date: 1996/08/31 Message-ID: #1/1 X-Deja-AN: 177689660 references: <509s75$4ps@map.mda.ca> organization: The World Public Access UNIX, Brookline, MA newsgroups: comp.lang.ada Date: 1996-08-31T00:00:00+00:00 List-Id: In article <509s75$4ps@map.mda.ca>, Ray Blaak wrote: >bobduff@world.std.com (Robert A Duff) writes: > >>How is: >> P'Identity >>different from: >> "P" > >P'Identity would be checked by the compiler. "P" is subject to typos, which >then gives misleading information in reporting (which are not always due to >exceptions, BTW. Consider tracing, debugging, etc.). OK, I suppose that makes sense. But to be useful, it seems like you would want other stuff as well. E.g., a way to get the caller of the current procedure, and its caller, and so on, so you can print out all those names. And line numbers of the calls. And names of all kinds of things other than program units. Shrug. It seems like a lot of information to keep around at run time, for a language like Ada. People already complain about the memory needed to store the tables for doing enumeration type 'Image. By the way, 'Identity is already used for a couple of other meanings. - Bob