From owner-freebsd-current Fri Aug 7 13:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13797 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:23:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13772 for ; Fri, 7 Aug 1998 13:23:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA03585; Fri, 7 Aug 1998 22:19:58 +0200 (CEST) To: Archie Cobbs cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 12:51:04 PDT." <199808071951.MAA04454@bubba.whistle.com> Date: Fri, 07 Aug 1998 22:19:57 +0200 Message-ID: <3583.902521197@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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