public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <gcc@gcc.gnu.org>
Subject: Ada documentation issues
Date: Fri, 05 Oct 2001 14:01:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0110052158240.12822-100000@kern.srcf.societies.cam.ac.uk> (raw)

There are several issues with the documentation of the Ada front end which
need to be resolved:

* The front end should have a proper manual, distributed in the ada
directory.  Once this is done, I will attend to updating
update_web_docs and onlinedocs/index.html to have that manual
available online.

* gcc/doc/install.texi needs updating: both to include ada in the list
of valid --enable-languages values, and to document exactly what needs
to be preinstalled in order to build the Ada front end.  As long as
there is a separate "make gnatlib_and_tools", this also needs to be
documented in install.texi.

* gcc/doc/contrib.texi should have GNU Ada contributors listed.

* gcc/doc/gcc.texi should be updated, both in the chapter "Compile C,
C++, Objective C, Fortran, Java or CHILL" and in "Language Standards
Supported by GCC" (the latter possibly pointing to where the GNU Ada
documentation describes Ada standards and GNAT's relation to them).

* gcc/doc/invoke.texi should have documentation added for suffixes for
Ada source files and for whatever -x language options there are for
Ada.

* Some more GNU Ada maintainers may need adding to MAINTAINERS.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

             reply	other threads:[~2001-10-05 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 14:01 Joseph S. Myers [this message]
2001-10-05 14:27 ` Geert Bosch
2001-10-09  4:14 ` Gerald Pfeifer
2001-10-09  4:20   ` Joseph S. Myers
2001-10-09 11:37     ` Gerald Pfeifer
2001-10-09 11:39       ` Geert Bosch
2001-10-05 14:41 mike stump
2001-10-05 14:48 ` Geert Bosch
2001-10-05 15:23   ` Joseph S. Myers
2001-10-05 15:33 mike stump
2001-10-06  8:17 dewar
2001-10-10  8:27 dewar

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=Pine.LNX.4.33.0110052158240.12822-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=gcc@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).