home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!pipex!demon!edscom!kevin
- From: kevin@edscom.demon.co.uk (Kevin Broadey)
- Subject: MSC-7.00, CC, CL386/CLMIPS and function prototypes
- Message-ID: <KEVIN.92Sep7113248@runningbear.edscom.demon.co.uk>
- Sender: kevin@edscom.demon.co.uk (Kevin Broadey)
- Organization: EDS-Scicon, Milton Keynes, UK
- Distribution: comp
- Date: Mon, 7 Sep 1992 11:32:48 GMT
- Lines: 34
-
- The application I'm porting to NT started life in Windows 2 and was
- written for version 5 of the Microsoft C compiler. It might even have
- been version 4. Anyway, in these pre-ANSI days you declared an external
- function in your .H file as:-
-
- int foobar (int foo, int bar);
-
- and you defined it in your .C file as:-
-
- int foobar (foo, bar)
- int foo;
- int bar;
- {
- ...
- }
-
- The problem is, this gets thrown out by the CC compiler on my R4000
- system. The same code compiles quite happily for Windows 3.1 using
- MSC-7.00.
-
- I've read in this newsgroup that CL386 is based on MSC-7.00, so does it
- allow this sort of code to go through?
-
- Also, according to Chapter 1: "C/C++ Compiler" in the SDK tools
- documentation taken from the July CD-ROM, CC will be replaced by CLMIPS.
- I assume this is CL386 with an R4000 code generator. If so, am I right
- in thinking that I don't need to edit my 100 or so source files to
- change the header style?
-
- --
- Kevin Broadey <kbroadey@edscom.demon.co.uk>
- EDS-Scicon, Wavendon Tower, Wavendon, Milton Keynes, MK17 8LX, England.
- Phone: +44 908 284198 (direct) or +44 908 585858 ext 4198
- These opinions are mine: others available on request.
-