home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!destroyer!cs.ubc.ca!uw-beaver!uw-coco!nwnexus!ole!rwing!fnx!nazgul!bright
- From: bright@nazgul.UUCP (Walter Bright)
- Newsgroups: comp.lang.c++
- Subject: Re: oopslooking for PerClass/SizeFreeList, oops
- Message-ID: <1566@nazgul.UUCP>
- Date: 10 Jan 93 01:08:23 GMT
- References: <1993Jan7.000515.11405@umr.edu>
- Reply-To: bright@nazgul.UUCP (Walter Bright)
- Organization: Zortech, Seattle
- Lines: 35
-
- In article <1993Jan7.000515.11405@umr.edu> S103408@UMRVMB.umr.edu writes:
- /Ok, BC++3.1 isn't working due to > 64K code segment.
- /Anybody out there have any experience with:
- /MetaWare High C++
- /Zortech C++
- /Watcom 9.0 C++
-
- I'll answer for Zortech C++.
-
- /that can tell me if these can do 32bit flat memory model coding
- /with dos and a dos-extender? Can I malloc() objects > 64K ?
-
- Yes and yes. No far or huge pointers, either.
-
- /Are there outrageous liscensing restrictions on the generated code?
-
- None at all (i.e. you can distribute/resell dos extender
- executables without any payment or permission from Symantec).
- You can't, of course, redistribute the development system!
-
- /Can I link in the extender or does it have to be already running?
-
- The extender links in and looks to the end user like just another
- DOS app. No device driver is required. It does not require
- Windows or 386MAX or QEMM to be running. It only requires a
- 386 or better. It doesn't even require more than 1Mb of memory
- to run...
-
- To build a simple 32 bit DOS extender app out of "hello world":
-
- ZTC -mx HELLO
-
- The only caveat is we don't ship a debugger for it (i.e. debug
- in a 16 bit model, and recompile for DOSX). Yes, I know this
- is suboptimal :-)
-