From owner-freebsd-arch Sun Oct 17 3:24:18 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 0A03D1506F for ; Sun, 17 Oct 1999 03:24:12 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id MAA00611 for ; Sun, 17 Oct 1999 12:24:10 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA67917 for freebsd-arch@freebsd.org; Sun, 17 Oct 1999 12:24:09 +0200 (MET DST) Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 9CAD41506F for ; Sun, 17 Oct 1999 03:23:54 -0700 (PDT) (envelope-from freebsd-arch@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA85069 for arch@FreeBSD.org; Sun, 17 Oct 1999 11:54:30 +0200 (CEST) (envelope-from freebsd-arch@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for arch@FreeBSD.org (arch@FreeBSD.org) To: arch@freebsd.org Date: Sun, 17 Oct 1999 11:54:19 +0200 From: Marcel Moolenaar Message-ID: <38099CCB.99EE1C97@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <3808BC30.2699465B@scc.nl>, <199910162136.PAA01266@harmony.village.org> Subject: Re: make world issues Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [taken of -arch] Warner Losh wrote: > Personally, I would have included backward compatibiltiy shims in libc > for the signal stuff for a while, but that appears to have been hard > to do... The problem I have with such a workaround (in general) is that it is difficult (in general) to know when you can remove the shims. Adding the shims is not the real problem. When the shims are there, they are either forgotten or alternatively, removing them starts long-threaded discussions which end up with the shims being kept because the persons in favor of removing them are generally less fanatical than the persons who are against its removal. When the shims are there long enough, no active developer knows why they are there in the first place and also decides to keep them because he/she fears world breakage and/or backward compatibility breakage. In the mean time other shims can be created with the workaround as precedent. Before you know it everybody is using shims without actually knowing why and you end up with a bloated set of libraries that, because of the shims and other compatibility stuff, are hard to maintain and bug-sensitive. Reverting such a situation is always more difficult than preventing it. In short: lot's of speculation :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message