🚀 go-pugleaf

Recently, brunix!sdm@uunet.uu.net (Scott) wrote:

> There are some problems with texing g++.texinfo I thought you might
> want to know about.

> ... notice the undefined cross references and the overly long lines.

These problems are relatively minor (but they SHOULD be fixed).  The
*real* problem is that g++.texinfo keeps falling further and further
behind G++ itself.  That's because Michael is more interested in hacking
than in documenting.  Who can blame him?  Let's face it.  Hacking is more
fun.  Still, it would be nice to have all of the quirky G++ options
and C++ extensions documented.  (I'm thinking of things like -fall-virtual
and things like case-ranges).

One suggestion I have for simplfying the maintenance of g++.texinfo is
to hack out all of the stuff that can be found in the gcc.texinfo file.
Rather that trying to constantly keep g++.texinfo up-to-date relative
to gcc.texinfo (as that document changes), I think it would be a lot
less work to simply say "see the GCC manual" in appropriate places in
the g++.texinfo file.  This would causes g++.texinfo to shrink
dramatically and there would be fewer problems with these two documents
getting out-of-sync.

Alternatively, perhaps g++.texinfo should be supplied *not* as a
standalone .texinfo file, but rather as a set of "patches" to the
gcc.texinfo file.  This way,  additions or deletions to the gcc
manual would automatically be reflected in the G++ manual.  Still,
the "patches" could add (or delete) information which is specific
to g++ (or gcc).

What about it Michael?  Will this help to make your job easier?

// Ron Guilmette  -  MCC  -  Experimental Systems Kit Project
// 3500 West Balcones Center Drive,  Austin, TX  78759  -  (512)338-3740
// ARPA: rfg@mcc.com
// UUCP: {rutgers,uunet,gatech,ames,pyramid}!cs.utexas.edu!pp!rfg