public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/5907: The Ada front end lacks a proper manual
Date: Sun, 10 Mar 2002 11:36:00 -0000	[thread overview]
Message-ID: <20020310193600.27035.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/5907; it has been noted by GNATS.

From: Florian Weimer <fw@deneb.enyo.de>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: <gcc-gnats@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>,  <brosgol@gnat.com>
Subject: Re: ada/5907: The Ada front end lacks a proper manual
Date: Sun, 10 Mar 2002 20:28:59 +0100

 "Joseph S. Myers" <jsm28@cam.ac.uk> writes:
 
 > On Sun, 10 Mar 2002, Florian Weimer wrote:
 >
 >> We would need a couple of hundered macros, I think.  For example, the
 >> preprocessing rewrites all strings like "hello.adb" to "HELLO.ADB",
 >> "hello.o" to "HELLO.OBJ", and so on.  If you had to write
 >> "@helloadb{}" and "@helloo{}", reading the sources would become rather
 >> difficult.
 >
 > Define a macro that's used like @vmsfile{hello.adb}{HELLO.ADB}.
 
 This still reduces readability to a certain extent.  In addition,
 there are about 100 command names and options which have to be
 replaced in the VMS version.  Of course, you could use the macro
 approach for this one, too, but we decided not to do that.
 
 Anyway, when I've finished writing the preprocessor, I can tweak it so
 that it writes a macroized Texinfo version, and we can still decide if
 we want to use this one, or the keep the preprocessor.
 


             reply	other threads:[~2002-03-10 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-10 11:36 Florian Weimer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06  2:26 Joseph S. Myers
2002-10-05 16:38 bosch
2002-03-10 11:06 Joseph S. Myers
2002-03-10  6:16 Florian Weimer
2002-03-10  3:56 Joseph S. Myers
2002-03-10  3:36 Florian Weimer
2002-03-10  3:06 Joseph S. Myers
2002-03-10  2:06 fw

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=20020310193600.27035.qmail@sources.redhat.com \
    --to=fw@deneb.enyo.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).