Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu!chad
From: chad@csd4.csd.uwm.edu (D. Chadwick Gibbons)
Newsgroups: comp.unix.wizards
Subject: Re: Weird problem with C compiler under SCO - I can't believe it!
Summary: blame microsoft
Message-ID: <95@uwm.edu>
Date: 17 Sep 89 01:01:40 GMT
References: <71@promark.UUCP>
Sender: news@uwm.edu
Reply-To: chad@csd4.csd.uwm.edu (D. Chadwick Gibbons)
Organization: University of Wisconsin-Milwaukee
Lines: 17

In article <71@promark.UUCP> mark@promark.UUCP (Mark J. DeFilippis) writes:
|The following short section of code does not compile using SCO XENIX 2.3.1
|and the 2.2.1 Development system, and I can't figure out why.
|1 main()
|2 {
|3 	char *cdecl;
|4 }

	The token "cdecl" is a reserved word under most implementations of
compilers developed for the Intel familiy of processors.  MicroSoft choosed to
use this to determine if a given function name was a "pascal," "fortran," or
C, i.e. "cdecl," function.  This convenction is followed by most DOS
compilers, and MicroSoft continues to use it--and they make the compilers for
SCO XENIX.  If you check the manual, there is a extended keyword flag
introducing "pascal," "fortran," and "cdecl."  -Me will turn on these flags.
more than likely, your compiler will have "-M3e" or some such as the default
flags.  Defining your own defaults will remove this action.