home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!mcsun!sun4nl!relay.philips.nl!prle!martens
- From: martens@prl.philips.nl (martens p)
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Re: quick C and FAQ
- Message-ID: <1992Dec21.124645.192@prl.philips.nl>
- Date: 21 Dec 92 12:46:45 GMT
- References: <Bz2I76.337@cs.columbia.edu> <1992Dec14.115454.12708@prl.philips.nl> <1992Dec18.105314.10867@comp.lancs.ac.uk>
- Sender: news@prl.philips.nl (USENET News System)
- Organization: Philips Research Laboratories, Eindhoven, The Netherlands
- Lines: 18
-
- In article <1992Dec18.105314.10867@comp.lancs.ac.uk> davei@comp.lancs.ac.uk (Mr D Ingles) writes:
- >In article <1992Dec14.115454.12708@prl.philips.nl> martens@prl.philips.nl (martens p) writes:
- >>In article <Bz2I76.337@cs.columbia.edu> smadja@cs.columbia.edu (Frank Smadja) writes:
- >>>1. What are the limitations of Quick C? Can you link any library or DLL
- >
- >Can someone tell me how one goes about upgrading QuickC for Windows for use
- >with Windows 3.1 ? I heard somewhere that you had to use the libraries from
- >Microsoft C7 to do it. If this is the case, which files do I need, and how
- >do I use them with QuicKC for Windows.
- >
- >Davei
-
- That is how I got it work: just replace the libraries and header files of
- QuickC with the ones that come with MSC7. That way you can also use the
- macro's that implement message maps and get rid of the ridiculous switch
- statements for processing messages. And then I discovered C++.
-
- Peter.
-