Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bobmon
From: bobmon@iuvax.cs.indiana.edu (RAMontante)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Request info on PC C compilers
Message-ID: <19893@iuvax.cs.indiana.edu>
Date: 21 Apr 89 03:37:38 GMT
Reply-To: bobmon@iuvax.cs.indiana.edu (RAMontante)
Organization: malkaryotic
Lines: 23

kevinf@infmx.UUCP (Kevin Franden) <1252@infmx.UUCP> :
-
-named differently, and of course borlant has their _own_ .lib format so you
-have to use their linker.

Not at all.  I have used both the MSDOS lib and link, with libraries created
by Borland's tlib, and everything goes fine.  Tlib and Tlink are faster but
somewhat less versatile than lib and link, but they are certainly compatible.

-<19500029@uxh.cso.uiuc.edu> phil@uxh.cso.uiuc.edu :
->
->High performance is desired in the run time package.  I'd trade off having
->my compiles take twice as long if it gives me even a 5% improvement in the

One of the current threads in comp.lang.c revolves around an msc
optimization level which produces incorrect far pointer code.  What is that
quote about the importance of generating the wrong answer quickly?

- TC will allow you to turn on/off all the portability or ANSI messages
- you care to.  It will even let you compile in ANSI-only mode

...by default.  I like to do everything by the book, so I have to go through
the menus and turn everything on.