home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!caen!hellgate.utah.edu!fcom.cc.utah.edu!dave
- From: dave@news.ccutah.edu (dave martin)
- Subject: Re: SAS/C 6.00 & ANSI & Strict and C='s includes (no prototypes)
- Message-ID: <1992Nov6.165213.17180@fcom.cc.utah.edu>
- Sender: news@fcom.cc.utah.edu
- Organization: University of Utah Computer Center
- X-Newsreader: Tin 1.1 PL3
- References: <Bx8xrD.5Br@unx.sas.com>
- Date: Fri, 6 Nov 92 16:52:13 GMT
- Lines: 20
-
- walker@twix.unx.sas.com (Doug Walker) writes:
- :
- : In article <1992Nov5.075836.27904@lmpsbbs.comm.mot.com>, rittle@supra.comm.mot.com (Loren James Rittle) writes:
- : |> In article <1992Nov4.192404.1147@jupiter.sun.csd.unb.ca> mctaylor@mta.ca writes:
- : |> >Why does my program get lots of warnings when I use ANSI and Strict for
- : |> >the messages, not from my program but from within the C= includes. The
- : |>
- : |> Because the fine people at C= haven't gotten around to updating the C=
- : |> includes to be %100 ANSI compliant. I hope that the 3.0 includes fix
- : |> these problems. Actually, I'll take the 3.0 includes in any form at
- : |> this time... :-)
- :
- : Actually, this is not true. The STRICT option in this case is being
- : more picky than ANSI requires.
-
- Well, there are also things like PWrite and PBothReady which cause a warning
- about no prototype defined, even without the STRICT option enabled.
-
- dave@csulx.weber.edu (ignore the header address, its probably wrong)
-
-