Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!gistdev!flint From: flint@gistdev.gist.com (Flint Pellett) Newsgroups: comp.os.msdos.programmer Subject: Re: Borland C++ 2.0 Message-ID: <1134@gistdev.gist.com> Date: 15 Feb 91 15:39:18 GMT References: <4698@gumby.Altos.COM> <1991Feb14.151804.6890@athena.mit.edu> <1991Feb14.204813.26432@spool.cs.wisc.edu> Organization: Global Information Systems Technology Inc., Savoy, IL Lines: 31 so@brownie.cs.wisc.edu (Bryan S. So) writes: >The brochure says: > Borland C++ gives you everything you need to generate > Windows programs and Dynamic Link Libraries (DLL's). > And with the included Whitewater Resource Toolkit, you > can visually create icons, bit maps, dialogs, menus and > other essentials for your Windows applications. Even > better, since Borland C++ gives you the MS Windows > header file and resource compiler, you don't need the > MS SDK. >I don't really know what a resource compiler is, can somebody >explain? I heard second-hand about a demo of this that was given: since I didn't see this first-hand, take it with a (big) grain of salt. The claim was that the demo showed them building some program in both the MS and Borland development environments on identical machines: the program took 50 seconds to build in the MS environment, 20 seconds in the Borland one. Then they changed something and rebuilt it: MS took another 50 seconds, Borland took 3. Apparently the difference on the second compile has something to do with pre-compilation of all the header file info that hardly ever changes (how often do you edit stdio.h ?) into a file that is saved and available to the second compile. I don't know if this is the "resource compiler" you mentioned, but it might be. -- Flint Pellett, Global Information Systems Technology, Inc. 1800 Woodfield Drive, Savoy, IL 61874 (217) 352-1165 uunet!gistdev!flint or flint@gistdev.gist.com