Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!wrgate!midas!cdb
From: cdb@midas.WR.TEK.COM (Christopher David Browne)
Newsgroups: comp.lang.c++
Subject: Re: C++ to C translator VS C++ compiler
Keywords: C++ translator, comparison, C++ Compiler
Message-ID: <3840@wrgate.WR.TEK.COM>
Date: 17 Oct 90 19:12:42 GMT
References: <16435@shlump.nac.dec.com>
Sender: news@wrgate.WR.TEK.COM
Reply-To: cdb@midas.WR.TEK.COM (Christopher David Browne)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 28

In article <16435@shlump.nac.dec.com> heintze@fmcsse.enet.dec.com (Siegfried Heintze) writes:
>At this time it appears that C++ will be our implementation language for 
>a product that must run on several UNIX(tm) flavored platforms in a addition
>to  VMS.
>
>We have also decided that VMS is going to be our development platform.
>
>Since all the target platforms are not clearly defined at this time, it appears
>wise to purchase a C++ to C translator.
>
>     products). 
Here at Tektronix we bought a C++ translator from Glockenspiel that was 
supposed to run on VMS. We found that you cannot link to a library module 
that contains a printf or cout statement.  We tried to find out how to
link from the manuals that we received but the manuals only covered 
the DOS os not VMS, we don't have a DOS platform.  We got nowhere with 
ImageSoft, Glockenspiels
outlet, with repeated calls for a month and a half. Then three or four weeks
ago ImageSoft found out from Glockenspiel that it was a known bug and 
that it was  fixed in a new releas and that they would mail that releas
to me post hast. 		I am still here waiting for it. I would 
not recommend the Glockenspiel C++ because of the customer assistance and
documentation. 

					Chris Browne
Disclamer: I speak for myself.