Date: Fri, 07 Aug 1998 22:19:57 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Archie Cobbs <archie@whistle.com> Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc Message-ID: <3583.902521197@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 07 Aug 1998 12:51:04 PDT." <199808071951.MAA04454@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199808071951.MAA04454@bubba.whistle.com>, Archie Cobbs writes: >> Yes, there is a memoryleak associated with use of this API, >> if that is unacceptable for your application then don't use this API. > >The attitude reflected in this statement is the exact opposite of mine, >which is: Yes, there is a memoryleak associated with use of this API, >let's fix the stupid bug and get on with it! Am I crazy for thinking >that? Yes, because as has been so elonquently pointed out to you by now, you cannot fix that leak without breaking a few conventions here and there and most likely some running code, for a very little actual benefit. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3583.902521197>