NetNews Usenet Archive 1992 #26/NN_1992_26.iso/spool/comp/os/msdos/programm/10503

Text File | 1992-11-11 | 1.6 KB | 42 lines

Newsgroups: comp.os.msdos.programmer
Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!slsvaat!us-es.sel.de!reindorf
From: [e-mail] (Charles Reindorf)
Subject: Re: 'new'ing >64K Objects in BC++
Message-ID: <[e-mail]>
Sender: [e-mail]
Organization: SEL-Alcatel Line Transmission Systems Dept. US/ES
References: <[e-mail]> <[e-mail]>
Date: Wed, 11 Nov 92 10:58:17 GMT
Lines: 30

In article <[e-mail]>, [e-mail] (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
|> [e-mail]
|>
|>
|>