Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!apollo!vasta
From: vasta@apollo.HP.COM (John Vasta)
Newsgroups: comp.sys.apollo
Subject: Re: troff to PS
Message-ID: <4e7152f2.20b6d@apollo.HP.COM>
Date: 6 Dec 90 23:49:00 GMT
References: <9010261101.AA04966@duc220.uni-duisburg.de> <9012061413.AA10010@hufsa>
Sender: root@apollo.HP.COM
Reply-To: vasta@apollo.HP.COM (John Vasta)
Followup-To: comp.sys.apollo
Organization: Hewlett-Packard Company, Apollo Division; Chelmsford, MA
Lines: 30

In article <9012061413.AA10010@hufsa> hanche@imf.unit.no (Harald Hanche-Olsen) writes:
>This letter I got from you is getting old:
>
>   Date: Fri, 26 Oct 90 12:01:19 +0100
>   From: hj412fr@duc220.uni-duisburg.de (Martin Anantharaman)
>
>I finally found some time to try compiling troff.  You said
>
>   I have installed groff with the Apollo C++ (c++.v.2.0.0) and only very
>   minor modifications were necessary: Some missing function prototypes if
>   you are in the BSD4.3 environment, customization of flags and printing
>   commands etc.
>
>However, it looks like ccxx insists that any file ending in .c is a
>plain C file, not a C++ file, and so it invokes the ordinary C
>compiler.  Needless to say, this breaks everything.  How did you get
>around this problem?  I suppose you could rename every *.c file to
>*.cxx and edit all the Makefiles, but I don't relish the thought.  If
>you found a more elegant solution, I would like to hear it.

If you have the last release of ccxx (Domain/C++ V1.2.2) you can
say "ccxx @.cxx=.c" to change the expected C++ filename extension
from .cxx to .c. But if groff is expecting C++ 2.0 behavior, you
probably won't get very far. Domain/C++ V2.0.0 allows any file
with an extension starting with 'c' or 'C' to be a C++ file.

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