From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dirk Herrmann Newsgroups: gmane.lisp.guile.devel Subject: Re: GC rewrite, first version. Date: Wed, 31 Jul 2002 19:03:28 +0200 (CEST) Sender: guile-devel-admin@gnu.org Message-ID: References: <15685.48166.358219.226421@blauw.xs4all.nl> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1028135036 25511 127.0.0.1 (31 Jul 2002 17:03:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 31 Jul 2002 17:03:56 +0000 (UTC) Cc: guile-devel@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17Zwt7-0006dC-00 for ; Wed, 31 Jul 2002 19:03:54 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17ZwtK-0001Vr-00; Wed, 31 Jul 2002 13:04:06 -0400 Original-Received: from sallust.ida.ing.tu-bs.de ([134.169.132.52]) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17Zwsp-0001Um-00 for ; Wed, 31 Jul 2002 13:03:36 -0400 Original-Received: from localhost (dirk@localhost) by sallust.ida.ing.tu-bs.de (8.9.3+Sun/8.9.1) with ESMTP id TAA00189; Wed, 31 Jul 2002 19:03:28 +0200 (CEST) Original-To: Han-Wen In-Reply-To: <15685.48166.358219.226421@blauw.xs4all.nl> Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.11 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:900 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:900 On Tue, 30 Jul 2002, Han-Wen wrote: > rlb@defaultvalue.org writes: > > Dirk Herrmann writes: > > > > > The problem with private headers is, that sometimes you like to > > > introduce some macros / function references which themselves are not > > > part of the API, but which you need to implement some macros (or - > > > in the not too far future - inline functions) that are part of the > > > API. This, however, means that these have to be part of the public > > > headers. This is one of the reasons we decided for the scm_i_ and > > > SCM_I_ prefixes. > > > > Oh right -- thanks -- I remember that now. That was a pretty good > > reason :> > > Well, if any of the private GC move to public headers, we can always > insert the I. Well, it has been said that as long as you are in the hacking phase, you shouldn't care about policy and naming, and I agree. And, I think that your changes will be a great step forward for guile. However, when you are going to add your stuff to CVS I think it is important that it does not deliberately violate conventions that have been agreed upon. Feel free to start a discussion about improving the convention, but until the decision is made to change things the way you like it, please follow the current convention when changing code in CVS. Best regards, Dirk Herrmann _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel