On Sat, May 13, 2017 at 07:55:44PM +1200, Evan Hanson wrote:
> Hi folks,
>
> Here are a few patches that deal with symbols and namespaces.
I've now applied the remainder of those patches.
> By way of example, the second uses this capability to refactor some
> internal helper procedures in
On Wed, May 17, 2017 at 01:29:32PM +1200, Evan Hanson wrote:
> Hi folks,
>
> > If there are no objections, I'll update the development process wiki page
> > accordingly and create a first snapshot from 38c4467f.
>
> This has been done, and the first CHICKEN 5 snapshot is now available at:
>
>
Hi folks,
> If there are no objections, I'll update the development process wiki page
> accordingly and create a first snapshot from 38c4467f.
This has been done, and the first CHICKEN 5 snapshot is now available at:
http://code.call-cc.org/dev-snapshots/2017/05/16/chicken-5.0.0pre1.tar.gz
> On 2017-05-15 9:24, felix.winkelm...@bevuta.com wrote:
> > I would like to elevate it to an official policy that patches that
> > break bootstrapping should only be pushed when there is a publicly
> > available snapshot tarball.
>
> That certainly makes sense to me.
>
> If there are no
On 2017-05-15 9:24, felix.winkelm...@bevuta.com wrote:
> I would like to elevate it to an official policy that patches that
> break bootstrapping should only be pushed when there is a publicly
> available snapshot tarball.
That certainly makes sense to me.
If there are no objections, I'll
> Please note that you will need to use a chicken (or a
> boot-chicken) that includes the first commit in order to build this
> second one.
I would like to elevate it to an official policy that patches that
break bootstrapping should only be pushed when there is a publicly
available snapshot
Hi Peter,
On 2017-05-13 11:58, Peter Bex wrote:
> Two quick questions: Given that C_namespaced_symbolp is inlineable and
> unsafe, shouldn't it be named C_u_i_namespaced_symbolp?
>
> And, given that it's inlineable, I think it would be better to put it in
> tweaks.scm (for example) as a
On Sat, May 13, 2017 at 07:55:44PM +1200, Evan Hanson wrote:
> The first changes the way explicitly-namespaced symbols are handled
> (that is, symbols with a module name directly included, like "foo#bar"),
> making them behave essentially like qualified symbols as far as variable
> resolution is
Hi folks,
Here are a few patches that deal with symbols and namespaces.
The first changes the way explicitly-namespaced symbols are handled
(that is, symbols with a module name directly included, like "foo#bar"),
making them behave essentially like qualified symbols as far as variable
resolution
