🚀 go-pugleaf

In article <14826@csli.Stanford.EDU> Neil Hunt <Neil%teleos.com@ai.sri.com> writes:
>In <32603@cup.portal.com> Chewy@cup.portal.com (Paul Frederick Snively) writes:
>
>>Hi, y'all!
>>I'm sure this is a rather stupid question, but I need to know...
>>To what extent are AT&T CFront 2.0 and g++ source-code compatible?
>
>It is generally a good idea to look before you leap.  I can't believe
>you site expires articles so fast that the following four were not
>available when you posted your question:
>	a Jim D 5 11-Y-03  14  porting tips for c++
>	b Jim ADCOCK       10  >
>	c George Wu       118  >
>	d Keith Nishihara  79  >>

I don't know about him, but on *our* machine they are expired.
Could someone e-mail them to me?

I'm also interested in the question of libg++ portability.
I recently tried to give my code (including the necessary libg++-include 
files and genclass generated code) away to someone who has only
a cfront clone and it could not deal with libg++'s use of GNU
extensions such as the use of named return values in String.h.

So my questions are:
1) Is there a cfront-compatable version of libg++ available,
   or better yet, a program to convert g++ extended code into
   standard c++ (alright maybe I'm dreaming).
2) How hard is it really to get libg++ stuff to compile under cfront

I'm not in a position to explore this on my own, since g++ is the
only c++ I've got (and I think its great!).

Donald Bashford
bashford@scripps.edu