From owner-freebsd-current Thu Apr 29 22:52:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7B1EE14E93 for ; Thu, 29 Apr 1999 22:52:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA11193; Thu, 29 Apr 1999 22:52:50 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA14825; Thu, 29 Apr 1999 22:52:50 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 29 Apr 1999 22:52:50 -0700 (PDT) Message-Id: <199904300552.WAA14825@vashon.polstra.com> To: sprice@hiwaay.net Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Steve Price wrote: > Fair enough, but the problem that really concerns me is that > all the C++ libraries (and the programs that use them) will have > to be recompiled when we make the switch. Is there a programatic > way to tell which vtable implementation a library was compiled > with? The compile-time error message doesn't count. Turning > the new vtable implementation on at any time now or in the future > is going to cause confusion. I guess the real question is will > turning it on by default now make for less problems than waiting > a month or two and then flipping the switch? These are good questions, and I don't know enough yet about the issues surrounding vtable thunks to answer them. We'll of course try to avoid the need to recompile libraries, but if that turns out to be impossible ... well, this is -current, after all. :-} John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message