🚀 go-pugleaf

In article <1992Oct28.155010.18287@mksol.dseg.ti.com>, dowte@mksol.dseg.ti.com 
(Terry E. Dow) writes...
>In article <1992Oct23.013421.20891@genie.slhs.udel.edu>, 
evh@genie.slhs.udel.edu (Troy Saville) writes:

>|> I am thinking about buying borland C++ and applications framework 3.1
>|> From what i understand,:
>|>   *) i need to use C++ in order to use applications frameworks
>|>   *) i can use applications frameworks under dos and windows.

>No, the framwork is for building Windows apps.

Not quite correct. "Application Frameworks" includes ObjectWindows and Turbo 
Vision.  ObjectWindows can be described as the application framework for 
Windows and Turbo Vision is the application framework for DOS.

>|>   *) can i generate 386 specific code(ie. 32 bit)?

>This version is not a 32 bit compiler.

This gets kind of tricky.  Borland C++ 3.1 does possess the capability to 
generate code which contains 386 instructions (use of the extended opcode 
set and opcode extension byte) but can not generate "true" 32 bit programs.

>|>   If it matters, i'm running a 20Mhz 386 with 4Mb ram and 105Mb hard disk.

>Speed has never been a problem for me, but then I haven't written a VERY large
>program.  4Mb is too small for any 386, I'd recommend 8Mb at least, but this 
>is not a Borland suggestion.

20 MHz shouldn't be a problem.  I would agree with the suggestion to go to 
at least 8MB RAM if you are going to develop for Windows in Windows.  You 
might be okay with 4 MB is you plan on doing only DOS.  105 MB might get a 
little cramped, unless you're running Stacker, Speedstor, or some other 
disk compression software.

JD