From owner-freebsd-threads@FreeBSD.ORG Wed Jun 18 23:34:59 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C74C37B401 for ; Wed, 18 Jun 2003 23:34:59 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id B057343FA3 for ; Wed, 18 Jun 2003 23:34:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfk2f.dialup.mindspring.com ([165.247.208.79] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19St0Z-0004UP-00; Wed, 18 Jun 2003 23:34:55 -0700 Message-ID: <3EF15947.1102D796@mindspring.com> Date: Wed, 18 Jun 2003 23:33:43 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Eischen References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4d198646b967cb52082105061744b4e11a2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: threads@freebsd.org cc: Kris Kennaway Subject: Re: Removal of bogus gethostbyaddr_r() X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2003 06:34:59 -0000 Daniel Eischen wrote: > On Wed, 18 Jun 2003, Terry Lambert wrote: > > Daniel Eischen wrote: > > > On Wed, 18 Jun 2003, Kris Kennaway wrote: > > > > Any objections? > > > > > > Why is this bogus? Do we have another gethostbyaddr_r hiding > > > somewhere? > > > > It lies? (_r). > > If that's true, then it's a bug and eventually should > be fixed. Yes. It's not thread-safe, and it's not reentrant, as implied by the name. I have no idea how it made it in past all the reviewing. > Additionally, you can't go around removing > public interfaces without bumping library versions > (unless said interface hasn't seen a release yet). That's a good point; but you'd hope that the binding of shared library symbols would be RTLD_NOW at compile time and RTLD_LAZY at runtime, so the only thing that would break are programs that actually used the symbol. And those programs are broken anyway, since if they depend on the thing working, they're broken. Maybe we could just declare an "void *" by that name that was equal to zero... 8-). But if no one is going to fix it before the next release, it should be diked out, because it's fooling "configure" prgorams (and unfortunately, just diking it out of the header files isn't enough, because they look by linking, rather than by looking). Makes you want minor version numbres back... -- Terry