[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GC rewrite, first version.
From: |
Han-Wen |
Subject: |
Re: GC rewrite, first version. |
Date: |
Tue, 30 Jul 2002 00:05:26 +0200 |
address@hidden writes:
> Dirk Herrmann <address@hidden> 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.
--
Han-Wen Nienhuys | address@hidden | http://www.cs.uu.nl/~hanwen
- GC rewrite, first version., Han-Wen, 2002/07/27
- Re: GC rewrite, first version., Rob Browning, 2002/07/28
- Re: GC rewrite, first version., Dirk Herrmann, 2002/07/29
- Re: GC rewrite, first version., Rob Browning, 2002/07/29
- Re: GC rewrite, first version.,
Han-Wen <=
- Re: GC rewrite, first version., Dirk Herrmann, 2002/07/31
- Re: GC rewrite, first version., Han-Wen Nienhuys, 2002/07/31
- Re: GC rewrite, first version., Rob Browning, 2002/07/31
- Re: GC rewrite, first version., Neil Jerram, 2002/07/31
Re: GC rewrite, first version., Michael Livshin, 2002/07/28