🚀 go-pugleaf

In article <MECHNER.95Jun20191937@blue.cs.nyu.edu>,
David Mechner <mechner@blue.cs.nyu.edu> wrote:
>
>
>I assume that the g++ team failed to get a repository working for
>2.7.0 but haven't updated this info page.  Is there a new target date?
>Even an estimate?
>

Mike Stump just posted a note on his -frepo patch to 2.7.0 official
release. There is a small note in the 2.7.0 release note posted in
various newsgroups (c.l.c++ eg) as to why this release does NOT include 
a repository mechanism. See Mike's Web page for more info on the
patch (http://www.cygnus.com/~mrs/) or get the patch via ftp from
ftp://ftp.cygnus.com/pub/g++/gcc-2.7.0-repo.tar.gz and rebuild gcc.

Just compiled a large piece of code that uses LOTs of templates and the 
repo mechanism did work; the only drawback, and predictable at that, is 
the increased compile and link time (ever used cfront-3.0.1 and 
derivatives on large templated projects?).

I'm probably going to stick with -frepo during the initial development of
a new piece of code and then move on to manual instantiation (easily done
by editing the repo files now, as opposed to the bad old days of running
``nm a.out | c++filt'' way). I'd like to create template closures for the
libraries and let the clients choose their instantiation method and, and
will investigate to see what works best.
.
mumit -- khan@xraylith.wisc.edu

Cc: mechner@blue.cs.nyu.edu