Xref: utzoo comp.sys.ibm.pc:41916 alt.msdos.programmer:1016
Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!jato!mars!kaleb
From: kaleb@mars.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.sys.ibm.pc,alt.msdos.programmer
Subject: Re: 386 instructions
Message-ID: <2569@jato.Jpl.Nasa.Gov>
Date: 12 Jan 90 20:43:18 GMT
References: <13346@garnet.BBN.COM> <580@watserv1.waterloo.edu> <3416@rti.UUCP>
Sender: news@jato.Jpl.Nasa.Gov
Reply-To: kaleb@mars.UUCP (Kaleb Keithley)
Distribution: comp
Organization: Jet Propulsion Laboratory, Pasadena, CA.
Lines: 22

In article <3416@rti.UUCP> bcw@rti.UUCP (Bruce Wright) writes:
>In article <580@watserv1.waterloo.edu>, batman@watsci.uwaterloo.ca (Marcell Stoer) writes:
>> If you want to issue 386 instructions, you will need a [C] compiler that
>> generates 32 bit code.  Microsoft has no such compiler.
>
>Maybe you meant to say that Microsoft has no such compiler at a reasonable
>price.  They most certainly *do* have a 32-bit version of their C compiler -
>it comes with their OS/2 V2.0 development kit (just shipping in the last
>month).  I haven't seen it, not doing OS/2 development, and it's rather
>expensive (the whole development kit costs $2600, counting documentation,
>compiler, developer's tools, etc).
>

Which means that they (Microsoft) doesn't have it.  Specifically, I can't
run down to Egghead or Software Etc and pick up a copy.  Not only that, but
this might imply that you have to run the compiler under OS/2, which not every
has, or wants, especially if you are developing for the DOS environment...

Chewey, get us outta here!
                 
kaleb@mars.jpl.nasa.gov             (818)354-8771
Kaleb Keithley