Date: Wed, 06 May 1998 17:55:44 -0400 (EDT) From: Greg Pavelcak <gpavelcak@philos.umass.edu> To: dwhite@resnet.uoregon.edu Cc: dwhite@gdi.uoregon.edu, Studded@san.rr.com, freebsd-questions@FreeBSD.ORG Subject: Re: malloc.h vs. stdlib.h Message-ID: <0ESK008T224FYU@rfd1.oit.umass.edu> In-Reply-To: <Pine.BSF.3.96.980506123642.10811F-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 May, Doug White wrote: > On Wed, 6 May 1998, Studded wrote: > >> When compiling someone else's stuff I often see warnings to the effect >> of, "warning, this file includes malloc.h which is a bad thing, please >> use stdlib.h instead." I am wondering if it's worthwhile to actually >> make that change in the software and recompile. > > Probably. That way we're sure it's using our enhanced malloc instead of a > local reimplementation. > I have seen this when installing ports too, and it seems strange to me. Couldn't the code that generates that message just direct the compiler to use stdlib.h instead and revert to malloc.h if stdlib.h is missing? Or is it left as a message because people may want to decide on a case by case basis which lib to use? Or perhaps it would just be really hard to do what I suggest. (I'm not a programmer, so I hope you'll excuse me if this is stupid rambling.) If it isn't too difficult, is there something I can do on my own machine to make the switch from malloc.h to stdlib.h automatic. Thanks. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0ESK008T224FYU>