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-Thread: 103376,34e28efa1a88ae84 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!w1g2000prd.googlegroups.com!not-for-mail From: Adam Beneschan Newsgroups: comp.lang.ada Subject: Re: Access procedure to pointer Date: Mon, 2 Jun 2008 08:35:09 -0700 (PDT) Organization: http://groups.google.com Message-ID: <0a18f3c1-ab3b-4f6d-9dfe-f348c69574ab@w1g2000prd.googlegroups.com> References: <483C48B5.9060303@gmail.com> <483D209D.5010408@gmail.com> <483D72F0.9090308@gmail.com> <49d0600f-e5cd-4d95-9ca4-1eb25a832437@l17g2000pri.googlegroups.com> <483DE480.9020208@gmail.com> NNTP-Posting-Host: 66.126.103.122 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1212420909 18870 127.0.0.1 (2 Jun 2008 15:35:09 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 2 Jun 2008 15:35:09 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: w1g2000prd.googlegroups.com; posting-host=66.126.103.122; posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.7.12-1.3.1,gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:526 Date: 2008-06-02T08:35:09-07:00 List-Id: On May 30, 10:52 pm, Stephen Leake wrote: > Sebastien Morand writes: > > There is so many packages in my adainclude directory, that make me > > sick not to know what is inside ;-) > > You could read the .ads files. They are well written and concise. Yes, and the file names are especially concise. What a joy to look at a directory listing of a directory containing 1,070 Ada sources all with names like i-forbla.ads and trying to figure out which one you need to look at to get your question answered. > I don't see what other form of documentation would be much better. Something, somewhere, that describes how the package works, in English (or maybe French, in Sebastien's case), and with a index so that you can find what you're looking for. Suppose you wanted to ask, "Does the GNAT library have a facility for handling UNIX signals?" The first place I'd look is in the manuals, either searching for "signal" or looking in the index for it. If, instead, I tried to use grep to search the .ads files for references to "signal", I'd find there are 27 of them, and in all probability I'd probably start by looking at g-signal.ads since that looks the most promising. That would probably lead to nowhere, unless maybe I could guess what to do next. But I think the idea that a library vendor can just release the sources of the package specifications and assume that will be enough documentation, is just plain wrong. -- Adam