From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.devel Subject: snarfer guard macro name decision: SCM_MAGIC_SNARFER Date: Tue, 12 Mar 2002 23:51:38 -0800 Sender: guile-devel-admin@gnu.org Message-ID: Reply-To: ttn@glug.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1016006443 15536 80.91.224.249 (13 Mar 2002 08:00:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 13 Mar 2002 08:00:43 +0000 (UTC) Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16l3gh-00042T-00 for ; Wed, 13 Mar 2002 09:00:43 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16l3fV-0008WR-00; Wed, 13 Mar 2002 02:59:29 -0500 Original-Received: from ca-crlsbd-u3-c5c-122.crlsca.adelphia.net ([68.64.59.122] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16l3aJ-00080o-00 for ; Wed, 13 Mar 2002 02:54:07 -0500 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16l3Xu-0004hF-00; Tue, 12 Mar 2002 23:51:38 -0800 Original-To: guile-devel@gnu.org Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:14 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:14 this was used in 1.4. libguile-1.6 .c source uses it as #ifndef, however both snarf.h and guile-snarf have been in the meantime changed to not define this. 1.6 snarfing differs from 1.4 primarily in that there are now two kinds: init and doc, as opposed to merely init. in defining the names of the specialization-trigger macros, we now remember usage of this old friend (i.e., also as guard). in the end, it is better to migrate self-guard naming internally, and include that info in the data stream only (snarfing programs generate program fragments opaque to all re-snarfing). so, this is sort of a good-bye from public view for SCM_MAGIC_SNARFER the cpp macro. [band plays.] anyone know what are the official namespaces allowed for programs that munge the cpp macro space? [macro looks up, wisened and ready for the inevitable coup. it is prepared to don a blade, but it has been heard that the really crafty old dictators (the ones who stayed alive) mingled and mewed and were the only ones allowed to slit their own throats.] thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel