public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Geert Bosch <bosch@gnat.com> To: bje@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/9406: Documentation suggestion Date: Thu, 20 Feb 2003 22:46:00 -0000 [thread overview] Message-ID: <20030220224600.30269.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/9406; it has been noted by GNATS. From: Geert Bosch <bosch@gnat.com> To: Simon Wright <simon@pushface.org> Cc: bosch@gcc.gnu.org, bje@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: ada/9406: Documentation suggestion Date: Thu, 20 Feb 2003 17:38:13 -0500 On Thursday, Feb 20, 2003, at 16:35 America/New_York, Simon Wright wrote: > You are of course entirely welcome to reject the suggested > rewording. However, > > (a) the first part of the patch corrected a grammatical error. Yes, I added to my initial reply that of course the grammar change was OK to apply. > My suggestion was to say "run the Ada binder on the Ada entry units" > but I suppose you could be all formal and say "run the Ada binder on > all the Ada units that contain subprograms that are called directly or > indirectly by the non-Ada main program". I think I would have > understood the former better. I certainly didn't understand the > present wording! > > (by the way, what about non-subprogram entities such as variables?) Actually, your "all formal" version shows some misunderstanding: you do not need to specify Ada units that are called indirectly by the non-Ada main program. Probably you are most helped by this quote from the Ada reference manual, 10.2(5): A partition is a program or part of a program that can be invoked from outside the Ada implementation. For example, on many systems, a partition might be an executable file generated by the system linker. The user can explicitly assign library units to a partition. The assignment is done in an implementation- defined manner. The compilation units included in a partition are those of the explicitly assigned library units, as well as other compilation units needed by those library units. This should also address your question about variables. -Geert
next reply other threads:[~2003-02-20 22:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 22:46 Geert Bosch [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-27 14:16 Ben Elliston 2003-02-23 14:56 Geert Bosch 2003-02-23 12:26 Simon Wright 2003-02-20 21:46 Simon Wright 2003-02-19 20:56 bosch 2003-02-18 14:06 bje 2003-02-18 12:09 bje 2003-01-22 20:56 simon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030220224600.30269.qmail@sources.redhat.com \ --to=bosch@gnat.com \ --cc=bje@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).