home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.programmer.misc:4504 comp.os.ms-windows.programmer.tools:1836
- Newsgroups: comp.os.ms-windows.programmer.misc,comp.os.ms-windows.programmer.tools
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!netcom.com!garylang
- From: garylang@netcom.com (Gary Lang)
- Subject: Re: MFC and Borland IDE
- In-Reply-To: stevesi@microsoft.com's message of 18 Dec 92 03:56:45 GMT
- Message-ID: <1992Dec29.164246.22111@netcom.com>
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- References: <61589@aurs01.UUCP> <1992Dec16.194955.19597@kth.se> <1992Dec18.035645.3257@microsoft.com>
- Date: Tue, 29 Dec 1992 16:42:46 GMT
- Lines: 21
-
- "The end result was (quoting the stats from the magazine):
-
- OWL MFC
- Lines of Code 3398 934
- EXE size(bytes) 56,848 46,536
-
- The OWL executable also requires 3 DLLs totalling 312,640 bytes. MFC
- is a stand-alone EXE.
- --
- Steven Sinofsky"
-
-
- Yes, but the results would have been similar if it had ben OWL vs.
- straight SDK calls Steve, and that's the point. The metric that
- matters is: how object-oriented is the app. fw. and is it removed
- enough from the toolbox of the platform to get me out of the business
- of worrying about allocating DCs and so on. For MFC, the answer is no.
-
- If I want speed and size and that's it, I'll code in assembler.
-
- -g
-