On Wed, Jul 23, 2014 at 07:56:01PM +1200, Evan Hanson wrote:
This is a cosmetic change that removes the ##sys# prefix from the
lambda-info names of procedures defined in library.scm. Where a
procedure was defined first with the prefix and later as an alias
without it, their definitions have
On 2014-07-23 10:06, Peter Bex wrote:
This change doesn't make much sense to me unless we also deprecate
the ##sys#-prefixed versions. ##sys#error sounds more internal or
primitive than error, so (to me) it makes more sense to have
error be an alias of ##sys#error, instead of the other way
On Wed, Jul 23, 2014 at 01:20:16AM -0700, Evan Hanson wrote:
On 2014-07-23 10:06, Peter Bex wrote:
This change doesn't make much sense to me unless we also deprecate
the ##sys#-prefixed versions. ##sys#error sounds more internal or
primitive than error, so (to me) it makes more sense to
From: Peter Bex peter@xs4all.nl
Subject: Re: [Chicken-hackers] [PATCH] Remove ##sys# prefix from lambda-info
names of library procedures
Date: Wed, 23 Jul 2014 10:24:59 +0200
On Wed, Jul 23, 2014 at 01:20:16AM -0700, Evan Hanson wrote:
On 2014-07-23 10:06, Peter Bex wrote:
This change
Felix Winkelmann felix.winkelm...@bevuta.com writes:
From: Peter Bex peter@xs4all.nl
Subject: Re: [Chicken-hackers] [PATCH] Remove ##sys# prefix from lambda-info
names of library procedures
Date: Wed, 23 Jul 2014 10:24:59 +0200
On Wed, Jul 23, 2014 at 01:20:16AM -0700, Evan Hanson
Peter Bex scripsit:
I'm not sure deprecating the prefixed versions is worth the hassle,
there are quite a few eggs using ##sys#error and ##sys#warn.
They should be fixed: the ##sys# API is undocumented and eggs that use
it are depending on something that's explicitly subject to change
without
From: John Cowan co...@mercury.ccil.org
Subject: Re: [Chicken-hackers] [PATCH] Remove ##sys# prefix from lambda-info
names of library procedures
Date: Wed, 23 Jul 2014 08:02:59 -0400
Peter Bex scripsit:
I'm not sure deprecating the prefixed versions is worth the hassle,
there are quite
Felix Winkelmann scripsit:
They can't be deprecated, as these procedures are used internally.
I know that that is so, but is there any reason why it must be so?
Could not internal use also be converted from ##sys#error to error, etc.?
But user/egg code should still not use it, of course.
A
John Cowan co...@mercury.ccil.org writes:
Felix Winkelmann scripsit:
They can't be deprecated, as these procedures are used internally.
I know that that is so, but is there any reason why it must be so?
Could not internal use also be converted from ##sys#error to error, etc.?
Well
Christian Kellermann scripsit:
Well deprecation is intended to give users of said procedures a heads
up and allows them to change their code in advance. Since this is all
internal API, I don't see the merit of such a process.
If only it were internal API, I'd say nothing. But it is de facto
10 matches
Mail list logo
