On Tue, 3 Jul 2007, Peter Hessler 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.
Yeah, but. This is a large application (16MB of source, zipped), old (1980's vintage), mixed-language (c, c++, fortran), used by engineers/scientists. It runs on several architectures and several OS's, including non-unix. It's not obsolete, and it's not broken. It is not just a matter of awk-ing the source code to replace these calls, there may be interactions with other code, including *unknown* code linked in by users in the field, some of it of ancient age, whose authors have died or wandered off to new jobs. Breaking (i.e. changing) the core routines is a bad idea. There are over a thousand instances of this warning, each warning generating at least 3 lines of output. (80col). This ceaseless nagging hides *real* bugs, (like the "No! ~I~ am Spartacus!" scene in the movie -- but I'm not looking for Spartacus, I'm looking for Maximus Bugicus.). That's over 100 pages of printout. I suppose this has been beaten to death, but lint-ing code is the job of lint, not the link-editor or compiler. Anyway, thanks to your hint, I believe the source of these messages is some sort of pragma/routine/whatever in the source code; it seems to be controlled by the make(1) variable APIWARN, set in .../src/libc/Makefile. I am a little bit loathe to rebuild libc at this point in the project, I'll just soldier on with the endless warning messages. Next "make release", though, I'll whack them to oblivion, if I remember. A second source of nagware is found in include files like malloc.h, they have to be individually silenced, I think. I demand the right to shoot myself in the foot. This is unix, after all! Thanks, Dave _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
