🚀 go-pugleaf

> 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.

  My current work group is looking into buying me an extender for analysis
  apps programs as the data is getting monsterous now.  I might then add
  that PharLap is our best choice since our work stations are mixed (2/3)86s.
  However it is rumored that BC++ 4.0 will have its own extender built in.
  The 3.1 upgrade is also said to have PharLap Lite (up to 2 meg only).

> 
> Currently I just don't use single arrays larger than 64K.  I do most
> of my programming under MS Windows (which is why I don't use DJGPP),
> so at least I have access to all my machines memory (Windows functions
> as a 16-bit DOS Extender).  A 16-bit Extender requires a 286 or
> better; a 32-bit extender requires a 386 or better.  Let me know if
> I'm wrong about any of this.

  In wonderment...  Should it not be an option to force 16-bit addressing
  out of a 32 bit extender?