public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: simon@pushface.org
To: gcc-gnats@gcc.gnu.org
Subject: ada/9406: Documentation suggestion
Date: Wed, 22 Jan 2003 20:56:00 -0000 [thread overview]
Message-ID: <20030122205551.7244.qmail@sources.redhat.com> (raw)
>Number: 9406
>Category: ada
>Synopsis: Documentation suggestion
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Wed Jan 22 20:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Simon Wright
>Release: gcc version 3.3 20021130 (experimental)
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
A slight lack of clarity wrt how to link with non-Ada mains: suggested patch..
--- gcc/ada/gnat_ug.texi 28 Dec 2002 21:38:51 -0000 1.6
+++ gcc/ada/gnat_ug.texi 22 Jan 2003 20:50:34 -0000
@@ -2409,7 +2409,7 @@
@cindex Binder output file
@noindent
-If the main program is in some language other than Ada, Then you may
+If the main program is in some language other than Ada, you may
have more than one entry point in the Ada subsystem. You must use a
special option of the binder to generate callable routines to initialize
and finalize the Ada units (@pxref{Binding with Non-Ada Main Programs}).
@@ -2440,7 +2440,7 @@
@end smallexample
@item
-Run the Ada binder on the Ada main program. For instance:
+Run the Ada binder on the Ada entry units. For instance:
@smallexample
gnatbind ^-n^/NOMAIN^ entry_point1.ali entry_point2.ali
@end smallexample
>How-To-Repeat:
n/a
>Fix:
Apply suggested rewrite
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-01-22 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 20:56 simon [this message]
2003-02-18 12:09 bje
2003-02-18 14:06 bje
2003-02-19 20:56 bosch
2003-02-20 21:46 Simon Wright
2003-02-20 22:46 Geert Bosch
2003-02-23 12:26 Simon Wright
2003-02-23 14:56 Geert Bosch
2003-02-27 14:16 Ben Elliston
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=20030122205551.7244.qmail@sources.redhat.com \
--to=simon@pushface.org \
--cc=gcc-gnats@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: link
Be 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).