Newsgroups: comp.os.minix
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!hermes.oc.com!news.unt.edu!cs.utexas.edu!howland.reston.ans.net!newsfeed.internetmci.com!EU.net!sun4nl!cs.vu.nl!kjb
From: kjb@cs.vu.nl (Kees J Bot)
Subject: Re: Compiler question about version 1.7-compiler
Nntp-Posting-Host: hornet.cs.vu.nl
References: <henze.7.310F36D1@hrz.uni-kassel.de>
Sender: news@cs.vu.nl
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Date: Wed, 31 Jan 1996 12:53:20 GMT
Message-ID: <DM1qGx.7sB.0.-s@cs.vu.nl>
Lines: 38

henze@hrz.uni-kassel.de (Rolf Henze) writes:

>Does anyone know about a compiler option to tell the compiler to accept old 
>fashioned code and to keep quiet? (Or could it be that the compiler has to be 
>at strict, not to mix 16- and 32-bit i386-mode?)

Observe:

	$ cat junk.c
	main()
	{
		const char *p = "10";
		extern long atol(char *);
		int i;

		i = 100000000000000;
		i = atoi(p);
		i = atol(p);
	}
	$ cc junk.c      
	"junk.c", line 2: (warning) 'main' old-fashioned function definition
	"junk.c", line 7: (warning) overflow in constant
	"junk.c", line 8: (warning) implicit declaration of function atoi
	"junk.c", line 9: (strict) qualifier error
	$ cc -wo junk.c  
	"junk.c", line 7: (warning) overflow in constant
	"junk.c", line 9: (strict) qualifier error
	$ cc -ws junk.c  
	"junk.c", line 2: (warning) 'main' old-fashioned function definition
	"junk.c", line 7: (warning) overflow in constant
	"junk.c", line 8: (warning) implicit declaration of function atoi
	$ cc -w junk.c   
	"junk.c", line 9: (strict) qualifier error
	$ cc -wa junk.c  
	$ 
--
	                        Kees J. Bot  (kjb@cs.vu.nl)
	              Systems Programmer, Vrije Universiteit Amsterdam
