🚀 go-pugleaf

In article <83366@ut-emx.uucp>, jamshid@ut-emx.uucp (Jamshid Afshar) writes:
|>
|> [ etc ]
|>
|> Maybe.  At least then you can write real C code without relying on
|> compiler extensions.  Btw, PharLap sells a DOS Extender that works
|> with BC++ or MSC.  I believe that a 16-bit Extender allows you to
|> access all your machine's memory (up to 16MB), but size_t and int are
|> still 16-bits, so each object is limited to 64K.  A 32-bit Extender
|> (like the one in DJGPP) makes them 32-bits so there are no 64K limits.
|> 

At this stage it should be pointed out that you need more than a 32-bit
extender to get rid of the annoying DOS limitations. You need a compiler
which generates code using 32-bit addresses in a flat addressing structure
(in protected mode). Currently, for DOS, this is the Zortech compiler, which
I personally have not used but which people say is good. It also has the 
necassary DOS extenders.

On the other hand, a 16-bit DOS extender can generally be used with code generated
by a normal 16-bit compiler and uses some mind-boggling jiggery-pokery to get it to
work.

|> [ etc ]
|> 
|> Jamshid Afshar
|> jamshid@emx.utexas.edu
|> 
|> 
|>