Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!mcgill-vision!sunkisd!vlsi3!thomasw
From: thomasw@vlsi3.CS.Concordia.CA (Thomas Wieland 1728423)
Newsgroups: comp.lang.c++
Subject: re: Re: What is C++ doing?
Summary: Compiler switch for Glockenspiel C++ compiler
Keywords: Glockenspiel
Message-ID: <853@sunkisd.CS.Concordia.CA>
Date: 31 May 89 01:54:23 GMT
References: <2671@ssc-vax.UUCP> <6590133@hplsla.HP.COM>
Sender: usenet@Sunkisd.CS.Concordia.CA
Reply-To: thomasw@jupiter.CS.Concordia.CA (Thomas Wieland 1728423)
Organization: Concordia University, Montreal Quebec
Lines: 33

In article <6590133@hplsla.HP.COM> jima@hplsla.HP.COM (Jim Adcock) writes:
>> ....  I have
>> Glockenspiel C++ on an Apollo, but I don't know how to get the
>> "compiler" to let me see it's C output.  (Anybody know?)

We have Designer C++ for our Suns (version 1.2, rel. 3d), which uses the
Glockenspiel compiler/preprocessor.  On our system, you can get the
C source by feeding the driver one of the following switches:

	@c,@k	compile, keep C source (.c) files generated by C++ compiler
	@t	translate C++ to C only, keep generated C source (.c) files

Also possibly useful:
	@p	compile, keep preprocessed C++ source files (.ixx, .i)

Note: options starting with "@" are case insensitive and can also start
      with "!", ie. "@c", "@C", "!c", and "!C" are all one and the same.

>So, the point being, even if you can get an intermediate "C"
>file, analysing what a C++ compiler is doing is a royal pain
>in the butt.
I agree wholeheartedly.

>Still, in the absence of documentation on what C++ compilers
>are doing, and why, this is the only real way to really learn the
>C++ language, and its implementations, so I think its worth
>the effort.
I have to agree again, unfortunately (with regard to lack of implementation
information.)


Thomas Wieland
thomasw@jupiter.cs.concordia.can