From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "John W. Eaton" Newsgroups: gmane.lisp.guile.user Subject: Re: deprecated symbol warnings Date: Sat, 14 May 2005 23:17:04 -0400 Message-ID: <17030.48944.683011.894315@devzero.bogus.domain> References: <41DEC762.765FDC9F@veritas.com> <41DED481.AEF0CABB@veritas.com> <170174E4-6347-11D9-9F67-000A95909EE2@raeburn.org> <5255fb95816d4cfc841223643e3481a8@raeburn.org> <4285F1CA.5070602@ossau.uklinux.net> <28ae757805033aac63a3f7bf8f4b1ccd@raeburn.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1116196009 10076 80.91.229.2 (15 May 2005 22:26:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 15 May 2005 22:26:49 +0000 (UTC) Cc: guile-user@gnu.org, Neil Jerram Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon May 16 00:26:06 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DXRYc-00083v-Dg for guile-user@m.gmane.org; Mon, 16 May 2005 00:25:59 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DXRDh-0000Fw-Rc for guile-user@m.gmane.org; Sun, 15 May 2005 18:04:21 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DXGlV-0005rL-S9 for guile-user@gnu.org; Sun, 15 May 2005 06:54:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DX9gZ-00021E-83 for guile-user@gnu.org; Sat, 14 May 2005 23:21:02 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DX9gW-0001xc-BW for guile-user@gnu.org; Sat, 14 May 2005 23:20:56 -0400 Original-Received: from [144.92.13.24] (helo=mail.cae.wisc.edu) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DX9lk-0008Vr-CU for guile-user@gnu.org; Sat, 14 May 2005 23:26:20 -0400 Original-Received: from portkey.cae.wisc.edu (portkey.cae.wisc.edu [144.92.13.118]) by mail.cae.wisc.edu (8.12.11/8.12.11) with ESMTP id j4F3Idih013831; Sat, 14 May 2005 22:18:39 -0500 (CDT) Original-Received: from devzero.bogus.domain (68-232-188-117.pittpa.adelphia.net [68.232.188.117]) (authenticated bits=0) by portkey.cae.wisc.edu (8.13.2/8.13.2/Debian-1) with ESMTP id j4F3IYWh013957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 14 May 2005 22:18:36 -0500 Original-To: Ken Raeburn In-Reply-To: <28ae757805033aac63a3f7bf8f4b1ccd@raeburn.org> X-Mailer: VM 7.19 under Emacs 21.4.1 X-CAE-MailScanner-Information: Please contact security@engr.wisc.edu if this message contains a virus or has been corrupted in delivery. X-CAE-MailScanner: Found to be clean (starburst) X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:4500 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:4500 On 14-May-2005, Ken Raeburn wrote: | >> /* N.B.: Application code will sometimes test whether one of these | >> macros is defined, to figure out if the version of Guile in use | >> predates the creation of the macro. So at deprecation time, we | >> still want the macro to be visible. ANSI C says "#define foo foo" | >> is okay, but if we get complaints about it, try switching the | >> non-macro name to "foo_" or "foo_deprecated" or something; make it | >> a simple concatenation so that we can make the other macros | >> continue to be simple. */ | > | > I think we should assume in advance that we'll hit trouble with this | > on some platforms. Otherwise it's just another hiccup to push people | > away from trying Guile out. | | *sigh* I was afraid of that. So when do we start requiring "real" | ANSI C support? :-( Can you point to a widely used compiler that will actually have trouble with this? If not, then maybe it is not worth worrying about? | Doing this means the compile-time messages will give the wrong symbol | names. They'll be close to the names used by the application, but not | the same. Still, getting messages that are close is probably better | than explaining to people why this strange use of the preprocessor is | actually valid and it's their compiler that's broken. I wonder if it's | really a problem these days, though, a decade and a half after the spec | was published.... Having the messages use the wrong names might cause a lot more confusion than having to explain to people that their compiler is broken. jwe -- jwe at octave dot org | Peace would shock and awe me. _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user