Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu From: dboles@ccwf.cc.utexas.edu (David Boles) Newsgroups: comp.sys.sgi Subject: C compiler question Message-ID: <48295@ut-emx.uucp> Date: 2 May 91 18:59:27 GMT References: Sender: news@ut-emx.uucp Reply-To: dboles@ccwf.cc.utexas.edu (David Boles) Organization: The University of Texas at Austin Lines: 18 I am having a problem with the MIPS C compiler. When I compile, I use the command cc -acpp -prototypes -p0. The p0 is there because the C compiler seems to get confused and generates profiling info. The main problem is that the -prototype option doesn't work correctly. There are no warnings generated when I compile code in which the function prototype does not match its definition! I can get by with just the acpp preprocessor for my macros, but function prototyping provides a very powerful way to keep your code healthy. Any comments? When is MIPS C going to be real C (i.e. ANSI)? -- ------------------------------------------------------------------------------- David Boles Applied Research Laboratories dboles@ccwf.cc.utexas.edu DOS is severely brain-damaged, apas611@chpc.utexas.edu so just pull the plug and let it DIE. -------------------------------------------------------------------------------