🚀 go-pugleaf

zcookbruc@cc.curtin.edu.au writes:
>I'm interested in hearing BORLANDs views on this (Am I even in the correct
>newsgroup?)
>
>For a while I've been hearing vague promisses from my local BORLAND office
>the BORLAND C++ would give me the option for 32bit code. (This implies to me
>that it would have to support some DOS extender, and behave socially towards
>other 32bit programs E.G. 386max, QEMM, etc). I've been waiting for the day
>especially since trying to use TD386, I have to re-configure my system
>(incidentally loosing memory, and networking) to use the debugger. This isn't
>a particularly good way to do things when debugging networking programms, or
>programms that use EMS.

Borland's Director of Product Management for Languages said in an open
forum that Borland expects to offer a 32-bit version of BC++ that supports
the Win32s API by the end of the year. He didn't provide more details.

But you don't need to reboot to use your debugger now for your 16 bit
work: TD386 may be incomapatible with 386 memory managers, but it's
TDH386.SYS that gives you access to hardware breakpoints, and
TD286.EXE will use that capability if TDH386.SYS is loaded. You can
even load TDH386.SYS high. The only significant difference between
TD386 and TD286 is that the latter occupies about 70K of low memory,
but you should get more than that back from your memory manager
anyway.

 -- sidney markowitz <sidney@borland.com>
 [disclaimer: I don't speak for Borland, I'm just quoting a
              spokesperson]