From owner-freebsd-hackers Thu Sep 9 2:52: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 4C24C14C32 for ; Thu, 9 Sep 1999 02:51:57 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id NAA91694; Thu, 9 Sep 1999 13:50:44 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id NAA01806; Thu, 9 Sep 1999 13:53:07 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199909090953.NAA01806@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Marcel Moolenaar Cc: Dmitrij Tejblum , hackers@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: 32+ signals and library versions In-reply-to: Your message of "Thu, 09 Sep 1999 07:54:09 +0200." <37D74B81.FDE66686@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Sep 1999 13:53:07 +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > > I suggest to try to avoid the version bump. NetBSD-like way to do it: > > Give new implementations another names in object files, so that they > > don't conflict with old implementations, and preserve old > > implementations in the library too. To make the compiler generate calls > > to new implementations, one can add appropriate #define s in .h files. > > For GCC, __asm__ attribute also can be used. > > That still is an interface change and thus needs a version bump. How else > do I know wich version x library has the new implementations (besides the > larger one :-)? No, when new functions are added into the library, and binaries linked with the old library will continue to work with new library, version bump is not required. This is a standard rule. It was also recently discussed on -committers on Aug 20 in the thread Re: cvs commit: src/include histedit.h src/lib/libedit Makefile editline.3 el.c el.h > How else > do I know wich version x library has the new implementations (besides the > larger one :-)? Linker knows it. If some function ("new implementation") is missing, linker print an error message. This is all you need. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message