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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a5449b9a03812b50 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-26 09:45:07 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-out.nuthinbutnews.com!propagator-sterling!news-in.nuthinbutnews.com!cyclone1.gnilink.net!washdc3-snf1!washdc3-snh1.gtei.net!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!dfw-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3D417647.CE3EC748@raytheon.com> From: Mark Johnson X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: GNAT documentation question References: <3D406C6B.9DE867E4@boeing.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 26 Jul 2002 11:18:15 -0500 NNTP-Posting-Host: 192.27.48.39 X-Complaints-To: news@ext.ray.com X-Trace: dfw-service2.ext.raytheon.com 1027700329 192.27.48.39 (Fri, 26 Jul 2002 11:18:49 CDT) NNTP-Posting-Date: Fri, 26 Jul 2002 11:18:49 CDT Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:27422 Date: 2002-07-26T11:18:15-05:00 List-Id: James Squire wrote: > > A.13.15 says: > The implementation shall document the conditions under which > Name_Error, Use_Error and Device_Error are propagated. > > I've looked through the GNAT Reference Manual and I can't find this > anywhere. Can anyone point me to where it is? Hmm. That is an interesting comment. There IS a description of when Use_Error is generated in the case of shared files (I know about that problem - we had code that needed fixing...). But in general, that description doesn't appear to be in ANY of the gnat documentation. Perhaps I should submit a bug report on it. On the other hand, it is a quick search to do something like... grep -inr "raise.*name_error;" /usr/gnat/lib/gcc-lib/i686-pc-linux-gnu/2.8.1/adainclude (rewrite the phrase and/or path as needed) to get the list of 5 locations where Name_Error is raised, the 14 locations for Use_Error, and 35 locations for Device_Error to get the REAL answer. I did this with a 3.16w version of gnat, the same search on 3.14a1 has slightly different results (3, 14, 33). If you also have glide, you could take that output, put the output of grep into a buffer, and enable compilation-mode to let you go directly to each reference. It would be far better to get it in the documentation, but this should help for now. --Mark