Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari!ames!pacbell!hoptoad!unisoft!mtxinu!sybase!orion!forrest
From: forrest@orion.sybase.com (Jon Forrest)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 3.0
Message-ID: <8475@sybase.sybase.com>
Date: 21 Feb 90 21:42:47 GMT
References: <1590@crash.cts.com> <3598@rti.UUCP>
Sender: news@Sybase.COM
Reply-To: forrest@sybase.com
Organization: Sybase, Inc.
Lines: 21

>
>I don't know anything about C++ (haven't had time to look at it),
>so I'm speaking from partial ignorance.  But what interests me is why
>everyone seems to think that a compiler that accepts both languages
>_must_ be slower even when compiling a program using just C.
[... lots of stuff edited out]

Your reply pretty much answers your question, especially if you
figure that Turbo C is targeted at 8088 class machines. Maybe
a combination C/C++ compiler won't be much slower that a C only
compiler (maybe) but it will certainly be bigger. On MSDOS big
is bad. On VM systems big isn't all that important.


----
Anything you read here is my opinion and in no way represents Sybase, Inc.

Jon Forrest WB6EDM
forrest@sybase.com
{pacbell,sun,{uunet,ucbvax}!mtxinu}!sybase!forrest
415-596-3422