🚀 go-pugleaf

(This report refers to version 1.35.0+ of G++)

I've started playing with G++ on Apollo's (using my gnu2coff object file
converter), and have noticed a couple problems with the 'extern "language"'
syntax.

First, 'extern "C"' is stricter in G++ than in other 2.0 implementations
of C++.  With 'extern "C"', G++ turns off the use of the "class" keyword
(among others); other 2.0 C++ implementations do not.  The specific example
I had locally is an "stdio" like header file that declared _iobuf as a class,
and all the various functions like getc, putc, etc. as friend functions of
the _iobuf class.  To keep names correct, this was all done within an
'extern "C"' bracket pair.

I also noticed that the 'extern "C++"' construct doesn't seem to work at all;
specifically it seems to produce the same effect as 'extern "C"'.

dgc