Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!taumet!steve
From: steve@taumet.com (Stephen Clamage)
Newsgroups: comp.lang.c++
Subject: Re: How compatible are the various C++ implementations?
Message-ID: <500@taumet.com>
Date: 3 Nov 90 16:51:01 GMT
References: <901012.051006.5031@nowhere.uucp> <475@taumet.com> <2391@lupine.NCD.COM>
Organization: Taumetric Corporation, San Diego
Lines: 18

rfg@NCD.COM (Ron Guilmette) writes:

>In article <475@taumet.com> steve@taumet.com (Stephen Clamage) writes:

|<For non-trivial C++ programs, the C code produced by the translator will not
|<necessarily work on arbitrary target machines.  For example, the
|<translator knows the sizes of data types (especially ints and pointers),
|<and generates references which depend on knowing those sizes.  If a
|<target uses other sizes, the C code will be wrong.  If you use the AT&T
|<cfront translator, you can purchase the source so that you can recompile
|<it for use with different targets.  It is, however expensive.

Since I posted that, I have been informed that AT&T cfront supports a
configuration file which allows you to specify machine-specific
features at C++ translation time.  I apologize for not checking this first.
-- 

Steve Clamage, TauMetric Corp, steve@taumet.com