🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.ibm.pc.programmer
Article #1219

Re: Help choosing C Compiler for specific use

#1219
From: John Burton
Date: Thu, 23 May 1991 13:10
92 lines
4915 bytes
In article <1991May23.064606.24717@unlv.edu> elvis@jimi.cs.unlv.edu (Frederick Haab) writes:
>In article <1991May22.225803.23546@cbnewsd.att.com> knudsen@cbnewsd.att.com (michael.j.knudsen) writes:
>>I'd like some advice on choosing between the many C compilers
>>available for MSDOS systems.  Before we get into good old religious
>>flame wars, let me say something about what I want it for:
>>
>I personally use Turbo C++, and with the included utilities you really
>only get the normal C keyboard routines, plus a couple of extra ones,
>and NO mouse support, although interupts are supported and you can
>write the routines yourself (I did.)
>

Look into the Borland C++ 2.0 package - it can be used for Windows 3.0
compliant programming and supports rodents...Its a nice slick package...
Its both a C++ compiler and an ANSI C compiler...
(Note, Borland sells two packages, Turbo C++ and Borland C++. Borland C++
is their "professional" version which comes with Assembler, Debugger, and
Profiler, plus a bunch of utilities for working with windows and creating
Hypertext help facilities)

>>Also I can never remember what .c file some function is in, so good
>>browsing tools would be nice.  I have a good Emacs editor so I
>>don't care about the built-in editor, tho I hear that Turbo forces
>>you to use their Wordstar-like editor (I could live with that).
>
>Turbo does NOT force you to use their editor.  With all the swapping
>the compiler does between memory and disk (I only have 640k), I
>often use a separate editor and a makefile.  The standard package
>does come with a make utility.
>

With Borland C++ you have many options as far as an editor goes... 
(I use Emacs on all the systems I work with...so why have to
learn a new one...:-). You can tailor the Wordstar Like editor that
they provide to emulate *most* (but not all) of what emacs does. 
Another alternative is that the Borland C++ (BC) Integrated Development
Environment (IDE) has hooks that let you tie in your favorite utility
or editor. I haven't used it so I can't tell you how it works. The
third option is using command line...BC has a Make facility (not strictly
UNIX compatible - but then again, many (most?) MSDOS Makes are not
UNIX compatible. BC comes with 2 seperate compilers: IDE and Command line.
Also included is a linker and library manager...

>>With Turbo C++ under $100 (?), it's tempting, but should I pay
>>extra for Microsoft C?  If I go Turbo, should I shell out extra for
>>their "Professional" version?

Why Pay extra for Microsoft C when it doesn't provide any additional
functionality?

>
>The professional version comes with Turbo assembler (this allows
>inline assembly language right inside your C code.) and the
>Turbo Profiler, which I believe helps in optimizing your code,
>but I don't have it so there may be more to it.
>
>>It must run on a Compaq II '286 with 640K and a 20 Meg HD
>>(or should I look for another computer, sheesh!?!)
>
>I run it on an XT with 640k and 20 meg HD, and it's slow
>(some of us students can't afford to just up and buy a
>new computer), but it works, and if it works on mine it'll
>more than likely work on yours.
>

Yup, Should work just fine on your machine...get BC 2.0
I think you'll be very happy with it...

>>All followups or email replies appreciated.  Thanks, mike k
>>-- 
>>"What America needs is A Thousand Points When Lit..."
>>
>>	knudsen@iceland.att.com
>
>	--==-- Frederick Haab --==--
>
>P.S. I posted so I can be corrected, but I'm pretty sure all
>     information is correct.


John


+--------------------------------------------------------------------+
| John Burton                                                        |
| G & A Technical Software                                           |
| jcburt@gatsibm.larc.nasa.gov                                       |
| jcburt@cs.wm.edu                                                   |
|                                                                    |
| Disclaimer: Hey, what can I say...These are *my* views, not those  |
|             of anyone else, be they employer, school, or government|
+--------------------------------------------------------------------+
Technical Details
Message-ID: <1991May23.131006.4934@news.larc.nasa.gov>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!sdd.hp.com!elroy.jpl.nasa.gov!news.larc.nasa.gov!ipsun.larc.nasa.gov!jcburt
References: <1991May22.225803.23546@cbnewsd.att.com> <1991May23.064606.24717@unlv.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!sdd.hp.com!elroy.jpl.nasa.gov!news.larc.nasa.gov!ipsun.larc.nasa.gov!jcburt
From: jcburt@ipsun.larc.nasa.gov (John Burton)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Help choosing C Compiler for specific use
Keywords: C
Message-ID: <1991May23.131006.4934@news.larc.nasa.gov>
Date: 23 May 91 13:10:06 GMT
References: <1991May22.225803.23546@cbnewsd.att.com> <1991May23.064606.24717@unlv.edu>
Sender: news@news.larc.nasa.gov (USENET Network News)
Organization: NASA Langley Research Center, Hampton, VA  USA
Lines: 92