Article View: comp.os.os2.programmer
Article #2639emx/gcc + workframe/2 + toolkit
From: Bill Sarantakos
Date: Mon, 21 Dec 1992 05:01
Date: Mon, 21 Dec 1992 05:01
28 lines
1740 bytes
1740 bytes
In article <1992Dec20.052158.18631@usage.csd.unsw.OZ.AU>, pendrith@spectrum.cs.unsw.oz.au (Mark Pendrith) writes: > >hi all, > >i'm quite enjoying using emx/gcc, but was wondering whether the workframe/2 >and toolkit (both of which are being offered by ibm at attractive prices at >the meoment) can be used with emx/gcc, or whether you have to use cset/2? > >also, could anyone briefly outline what the workframe/toolkit stuff actually >gives you? any good books that complement their use? thanks in advance. WorkFrame/2 was designed for use with any compiler. In fact, you can plug in your own editor, debugger, maker, and linker. Then you can add many of your other preferred tools to its 'Tools' menu. This is very different from the 'other' development environments who force you to use their own tools. WorkFrame/2 also implements many drag & drop features which allow you to do your work more easily. When used with the enhanced editor, the error handling mechanism is quite powerful. It also provides a default compiler dialog for those compilers that don't yet provide WorkFrame/2 support. Those that do include Watcom, Symantech, and Borland. Bill Sarantakos OS/2 C++ compiler development Of course the above is just my biased opinion! ;-)
Technical Details
Message-ID:
<19921220.210155.3@almaden.ibm.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.comReferences:
<1992Dec15.111141.1650@edfd.uucp> <1992Dec20.052158.18631@usage.csd.unsw.OZ.AU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.com From: bigbill@vnet.ibm.com (Bill Sarantakos) Message-ID: <19921220.210155.3@almaden.ibm.com> Date: Mon, 21 Dec 92 00:01:56 EST Subject: emx/gcc + workframe/2 + toolkit Newsgroups: comp.os.os2.programmer References: <1992Dec15.111141.1650@edfd.uucp> <1992Dec20.052158.18631@usage.csd.unsw.OZ.AU> Organization: IBM Corporation Disclaimer: This posting represents the poster's views, not those of IBM Lines: 28