Xref: utzoo gnu.g++.bug:655 comp.sys.apollo:2728
Path: utzoo!utgpu!watmath!uunet!tektronix!psueea!qiclab!mntgfx!dclemans
From: dclemans@mntgfx.mentor.com (Dave Clemans @ APD x1292)
Newsgroups: gnu.g++.bug,comp.sys.apollo
Subject: G++ 1.35 extern "language" problems
Message-ID: <1989May25.095451.21761@mntgfx.mentor.com>
Date: 25 May 89 16:54:50 GMT
Organization: Mentor Graphics Corporation, Beaverton Oregon
Lines: 18

(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