Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!cs.umn.edu!msi.umn.edu!math.fu-berlin.de!unidui!veit From: veit@du9ds3.uni-duisburg.de (Holger Veit) Newsgroups: comp.os.msdos.programmer Subject: Re: Difference Between Turbo C++ and Turbo C++ 2nd Edition Message-ID: Date: 23 May 91 06:26:10 GMT Article-I.D.: du9ds3.veit.674979970 References: <00948F19.88197060@MAPLE.CIRCA.UFL.EDU> <1991May22.002318.19357@borland.com> <2705@pdxgate.UUCP> <1991May22.214156.24610@eecs.nwu.edu> Sender: @unidui.uni-duisburg.de Organization: Rechenzentrum Uni-Duisburg Lines: 29 In <1991May22.214156.24610@eecs.nwu.edu> kaufman@eecs.nwu.edu (Michael L. Kaufman) writes: >In article <2705@pdxgate.UUCP> jita@eecs.cs.pdx.edu (Hengky Jita) writes: >>About the Windows support and the protected mode tools included in the >>Borland 2.0 package, do we still need to get the MS Software Development >>Toolkit package in order to write Windows program if we have had Borland 2.0? >No. Yes and No. The software tools are quite complete (Whitewater Resource Kit, tdw, rc, implib, link, etc.), but the bookware isn't. The documentation tells not a word about the available callable Windows functions, that are in the IMPORT library. Borland explicitly recommends that programmers buy the SDK documentation seperately, or at least a book on windows programming. Also, I heard (I do not have SDK) that SDK not only contains development tools, but also a "transformation kit" which allows conversion of former files (e.g. *.ico files, the format of which has been changed from 2.xx to 3.00). I found that out by simply trying to compile a 2.03 example from the SDK 2.0 with BC. This worked (nearly) but then rc complained about incompatible files. Holger -- | | / Holger Veit | INTERNET: veit@du9ds3.uni-duisburg.de |__| / University of Duisburg | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO | | / Fac. of Electr. Eng. | UUCP: ...!uunet!unido!unidui!hl351ge | |/ Dept. f. Dataprocessing |