Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!apollo!vasta
From: vasta@apollo.HP.COM (John Vasta)
Newsgroups: comp.sys.apollo
Subject: Re: c++ with cc6.8
Summary: use -W0,-ncompress
Message-ID: <50770f38.20b6d@apollo.HP.COM>
Date: 19 Mar 91 22:33 GMT
Sender: root@apollo.HP.COM
Reply-To: vasta@apollo.HP.COM (John Vasta)
Organization: Hewlett-Packard Company, Apollo Division; Chelmsford, MA
Lines: 28

In article <WIM.91Mar14122747@eutes3.es.ele.tue.nl> wim@es.ele.tue.nl (Wim Philipsen) writes:
>
>At about the same time we recieved out at&t C++ front-end with the cc6.7, and
>on an other tape 6.8. Did anybody have problems with the combination c++ and
>cc6.8?

From the release notes for C 6.8 (section 1.10: C++ compatibility):

     To  ensure  compatibility  between  Domain/C Version 6.8 and either version of
     Domain/C++, compile your C++ source files with the -W0,-ncompress option. If
     you  do  not  use  -W0,-ncompress,  constructors  and  destructors  for static
     objects will not execute correctly. 

     To ensure compatibility between Domain/C Version 6.8  and  Domain/C++  Version
     2.0.0,  do  not declare any virtual function inline.  If you declare a virtual
     function inline, a bug in the C++ translator causes it to  generate  incorrect
     C  code, and the C compiler issues an error message.  Since the C++ translator
     ordinarily does not perform inline  expansion  of  virtual  functions  in  any
     case, this restriction usually has no effect on the quality of your code. 

Domain/C++ 2.1 (which should be shipping now) supports the use of compressed
data, so if you get it you can stop turning compression off. The problem with
inline virtual functions still exists, however.

John Vasta                Hewlett-Packard Apollo Systems Division
vasta@apollo.hp.com       M.S. CHR-03-DW
(508) 256-6600 x5978      300 Apollo Drive, Chelmsford, MA 01824
UUCP: {decwrl!decvax, mit-eddie, attunix}!apollo!vasta