He knows that. He's working on an old app that uses those; he'll remove them once he gets the app actually /working/.
Woodchuck: maybe you could just use grep to filter out the warnings? On 7/3/07, Peter Hessler <[EMAIL PROTECTED]> wrote: > There isn't a switch, its a chunk of code. Theoretically, you could > remove the diff. Don't know where/when it happened though. > > Keep in mind, that so many people screwed up using strcat(), sprintf(), > that openbsd decided to mark them as deprecated. Its possible to use > them safely, but its unlikely. Obsolete and broken code should be > viewed carefully, preferably with peril-sensitive glasses. > > > On 2007 Jul 03 (Tue) at 20:15:37 -0400 (-0400), Woodchuck wrote: > :What's the switch to gcc to turn off the nagging about strcat(), > :sprintf() and so forth? This is really inhibiting my productivity > :in porting a large application from the past. I've already > :made it shut up about malloc.h (change /usr/include/malloc.h). > : > :2/3 of compilation output, or more, consists of these nannyish > :warnings. > : > :Dave > :-- > : Resistance is futile. You've already been assimilated. > > > > -- > Love cannot be much younger than the lust for murder. > -- Sigmund Freud > _______________________________________________ > Openbsd-newbies mailing list > [email protected] > http://mailman.theapt.org/listinfo/openbsd-newbies > _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
