Path: utzoo!attcan!uunet!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!ncar!ico!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: Is there a good example of how toupper() works?
Message-ID: <18588@haddock.ima.isc.com>
Date: 20 Oct 90 00:40:39 GMT
References: <wb76pN600awOE3SaQz@andrew.cmu.edu> <1990Oct17.170914.683@wpi.WPI.EDU> <18575@haddock.ima.isc.com> <1990Oct19.145302.24826@bbt.se>
Reply-To: karl@ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 9

In article <1990Oct19.145302.24826@bbt.se> pgd@bbt.se writes:
>Is there some special benefit of saying "/usr//include" instead of
>"/usr/include"?

Yes.  It kludges around the warning provided by some compilers that believe
it's a bad idea to explicitly #include from /usr/include.  (I agree with them,
but since I don't have a good alternative, I do it anyway.)

Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint