Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!nowhere!sking
From: sking@nowhere.uucp (Steven King)
Newsgroups: comp.lang.c++
Subject: Re: How compatible are the various C++ implementations?
Message-ID: <901012.051006.5031@nowhere.uucp>
Date: 12 Oct 90 05:10:06 GMT
Organization: nowhere
Lines: 37

In Message <34661@cup.portal.com> ts@cup.portal.com (Tim W Smith) writes:

>We are thinking of moving from C to C++ as our primary
>development language at work.  Before doing this, we
>need to make sure that we can get a set of compilers
>across various platforms that are compatible.

>Most of our work is with standalone systems.  Right now,
>we tend to use Turbo C or Microsoft C to write our stuff
>if the target system has an 8086 family CPU, and Think C
>if the target has a 68000 family CPU.  We take the output
>of the compiler, wrap it in standalone "glue", and stick
>it in the standalone system.

	[ other stuff about compatiblity between various target platforms ]

   It was for these same reasons (and cost as well) that I choose a translator
as opposed to a native code compiler. Instead of purchasing seperate C++ 
compilers for each target (even assuming they were availible) I have a single
C++ translator running on my host platform (386 unix) that can produce C source
for 8051, v40 (a 80186 sort of), 68k, this here box, or anything else that has
a C compiler for it. I dont have to worry about compatibility at the C++ level
since the C output is the same for each target, one only needs to evaluate the
capabilities of the target C compiler.
 
  Also by using a translator, one has the option of editing the C output to
correct any "deficiencies" -- usually not fun, but occasionally neccessary,
especially for embedded systems work where ones execution enviroment doesnt
match traditional general purpose computers (code in ROM, discontiguous memory
spaces, etc.)


-- 
-------------------------------------------------------------------------------
new && improved:			 			 sking@nowhere
old && reliable:			...!cs.utexas.edu!ut-emx!nowhere!sking
-------------------------------------------------------------------------------