Path: utzoo!attcan!uunet!mcsun!unido!gmdzi!strobl From: strobl@gmdzi.gmd.de (Wolfgang Strobl) Newsgroups: comp.windows.ms Subject: Re: how not to develop in SDK Message-ID: <3504@gmdzi.gmd.de> Date: 28 Oct 90 14:17:05 GMT References: <5270@crash.cts.com> Organization: GMD, Sankt Augustin, F. R. Germany Lines: 41 alen@crash.cts.com (Alen Shapiro) writes: >Did you know (and not a lot of people know this :-)) that... No, but thanks for the info. What mode are you running Windows 3 in? >You can't be in the MSWindows 3.0 environment and compile an >MSC 6.0 program so that you can remain in the environment >while you compile-debug your windows application (SDK). >The compiler runs out of heap space!! ... > ... >Comments/hints suggestions on the above anyone? Try Zortech C++ (or C, it comes with C++) version 2.1. From one of the readme files which come with the compiler: "The Dos-Extender used in the Zortech C++ compiler and the Zortech C++ Workbench is compatible with Windows 3 and uses the DMPI standard. This means that large dos or Windows applications can be compiled from within the Windows environment. Zortech supplies two Windows 3 Icon files and example PIF files for the command line compiler and the C++ Workbench. The Icon files are ZTC.ICO and ZWB.ICO. ... NB. If you wish you can use the command line parameters option in the PIF file to set the Dos-Extended compilers as the default using the -br flag." I haven't tried to push it against the limits by compiling very large programs, but my programs aren't very small, either. I do all my work including editing and compiling Windows programs, from within the Windows environment. I don't use the Zortech Workbench, because I like my ad hoc collection of pif files and program groups better. I cannot compare the Zortech compiler to MSC 6, because we don't have it here, yet. Wolfgang Strobl #include