swonk@ccicpg.UUCP (Glen Swonk) (06/05/90)
I saw a message on the net that someone had created some MS Windows classes for Zortech C++. Has anyone else seen these and if so, could you point me in that direction. Also, are there people out there actively using C++ (Zortech or Glockenspiel?) for MS Windows development or just experimentation? thanks glenn -- Glenn L. Swonk CCI Computers (714)458-7282 9801 Muirlands Boulevard Irvine, CA 92718 uunet!ccicpg!swonk
strobl@gmdzi.UUCP (Wolfgang Strobl) (06/06/90)
swonk@ccicpg.UUCP (Glen Swonk) writes: >Also, are there people out there actively using >C++ (Zortech or Glockenspiel?) for MS Windows development >or just experimentation? I looked at the old version of Glockenspiel and decided to wait for an upgrade to the current version. At home I try to use Zortech (2.06) , with mixed results. The C compiler is fine, it does all I want. So far I could not get real C++ work with Windows; in order to make virtual member functions work I have to make my code segment FIXED (which isn't very nice). In the UK BBS of Zortech I found the tip (in WINTIPS.DOC) that in order to have moveable code segments one has to use LINK4 version 5.02 (with my latest SDK 2.11 came a version 5.01.something). I haven't called Microsoft, yet. Does anybody know which version of link4 is current? What about the LINK.EXE which come with OS/2 1.1 and 1.2? What about thhe LINK.EXE from the IBM Version of the MSC compiler (version 1.1)? Are these possible replacements of the toolkit (SDK) LINK4s? Are they newer, older or what? What is contained in the (beta?) SDK of windows 3? Wolfgang Strobl PS please excuse my language and my typos, english isn't my native language, and vi is definitely not my native editor ;-) o
tomr@ashtate (Tom Rombouts) (06/06/90)
In article <74771@ccicpg.UUCP> swonk@ccicpg.UUCP (Glen Swonk) writes: >I saw a message on the net that someone had >created some MS Windows classes for Zortech C++. >Has anyone else seen these and if so, could you >point me in that direction. > As of last week, Robert Swarm of Zortech told me there were two, but both are in beta. One is the Tier C++ Object Library for Windows, advertised on page S/16 of the May 22, 1990 "PC Week" MS-Windows section. (Voice #: (817) 965-2602) I do not know the name of the other, but Mr. Swarm did. He seems like a good guy, and could likely be contacted directly at Zortech. Tom Rombouts Torrance Techie Voice: (213) 538-7108 (The opinions above are my own and may or may not have a high correlation to reality as it is commonly known.)
strobl@gmdzi.UUCP (Wolfgang Strobl) (06/06/90)
strobl@gmdzi.UUCP (Wolfgang Strobl) writes: >in order to have moveable code segments one has to use >LINK4 version 5.02 (with my latest SDK 2.11 came a version Oops, that should have been SDK 2.10. Sorry >5.01.something). Wolfgang Strobl, STROBL@DBNGMD21.BITNET
brianf@umd5.umd.edu (Brian Farmer) (06/07/90)
In article <2513@gmdzi.UUCP> strobl@gmdzi.UUCP (Wolfgang Strobl) writes: >strobl@gmdzi.UUCP (Wolfgang Strobl) writes: > >>in order to have moveable code segments one has to use >>LINK4 version 5.02 (with my latest SDK 2.11 came a version >Oops, that should have been SDK 2.10. Sorry >>5.01.something). > There was an extra link included with MSC 5.1 for use with OS 2 but that didn't get installed if you only installed for DOS. I don't remember which disk it is on but the size is about 110k and is called LINK. You can use this linker just like LINK4 except you need to include the line 'EXETYPE WINDOWS' in your .def files.
strobl@gmdzi.UUCP (Wolfgang Strobl) (06/08/90)
brianf@umd5.umd.edu (Brian Farmer) writes: > There was an extra link included with MSC 5.1 for use > with OS 2 but that didn't get installed if you only > installed for DOS. I don't remember which disk it is > on but the size is about 110k and is called LINK. > You can use this linker just like LINK4 except you need > to include the line 'EXETYPE WINDOWS' in your .def files. I do not have MSC 5.1, but I have IBM C/2 1.1, which is essentially the same compiler (at least it has excactly the same bugs :) Its LINK.EXE (107 230 Bytes) has no documented EXETYPE statement in the Module Definition FIle, but understands it anyway. I had tried this LINK.EXE before, without the EXETYPE statement. It is not necessary for producing MS Windows programs. But with this LINK (instead of the 5.01 LINK4) my virtual member functions do not work, either. I tried your suggestion anyway. With this statement included in the .DEF file, the linkage editor produces a .EXE file of exacly the same length, with only one bit changed (offset 40a, from B6 to B7). The EXEHDR utility doesn't know this bit, and it has no noticeable effect. Does anybody out there have an LINK4 version 5.02 or later? How old is it (time stamp)? From which SDK version is it? Wolfgang Strobl