Xref: utzoo comp.lang.c:40416 comp.lang.c++:14354
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!swrinde!elroy.jpl.nasa.gov!decwrl!megatest!djones
From: djones@megatest.UUCP (Dave Jones)
Newsgroups: comp.lang.c,comp.lang.c++
Subject: Re: Porting Cfront's output to other systems.
Message-ID: <19177@prometheus.megatest.UUCP>
Date: 25 Jun 91 00:37:10 GMT
References: <1991Jun21.211157.10040@starnet.uucp>
Organization: Megatest Corporation, San Jose, Ca
Lines: 12

From article <1991Jun21.211157.10040@starnet.uucp>, by dror@starnet.uucp (Dror Matalon):

> 4. Any other issues?

I'm using a pure-compiler version of c++ now, but the version of cfront
that I used to have produced C code that had already effectively had a cpp
done on it. Therefore, you'll have to be sure that the #include-files
the compiler finds are for the target machine and target-machine libraries,
not for the host machine. Beware of any #ifdef switches on the machine
type in the source code or in the #include-files. Better yet, get a
C++ compiler for the target machine, and don't even try to port the
derived C code.