This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: ada/5907: The Ada front end lacks a proper manual
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Florian Weimer <fw at deneb dot enyo dot de>
- Cc: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, <gcc-bugs at gcc dot gnu dot org>, <brosgol at gnat dot com>
- Date: Sun, 10 Mar 2002 09:28:11 -0500 (EST)
- Subject: Re: ada/5907: The Ada front end lacks a proper manual
On Sun, 10 Mar 2002, Florian Weimer wrote:
> "Joseph S. Myers" <jsm28@cam.ac.uk> writes:
>
> > On Sun, 10 Mar 2002, Florian Weimer wrote:
> >
> >> The VMS version requires substantial postprocessing (words are
> >> replaced globally, file names are rewritten). It is not possible to
> >> express this in Texinfo.
Yes it is:
def: @set GCC gcc
use: @value{GCC}
Not that it's a solution here.
> > Why not? If the standard manual needs the word "foo", where the VMS
> > manual needs "bar", why shouldn't a macro @foo{} (with different
> > definitions in the two cases) work?
>
> 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.
Can't you make @file{} or an equivalent do that transformation?
If the docs are as other doc files in the tree, it would already
use @file{} around file names.
brgds, H-P