On Sat, May 27, 2017 at 03:34:54PM +1200, Evan Hanson wrote:
> Yeah, let's leave it at that. It's easy enough to convert property lists
> to something else as needed. I'm also not too worried about breaking
> changes here, so I've applied your patch as-is and updated the
> `condition->list`
On Wed, May 24, 2017 at 08:58:46AM +0200, Peter Bex wrote:
> That's requires more keystrokes, but at the same time it's more readable.
> Of course one reason to add the constructor is to have an API that's
> less verbose, and this adds back a little bit more verbosity. On the
> other hand, the
Hi Peter,
Nice work, this is a great idea.
I'm definitely in favor of a procedure like this, but I do have one
thought regarding the specifics: the procedure `condition->list` already
defines a convention of sorts for representing the constituent parts of
a condition as data, whereas this new
On Fri, May 19, 2017 at 01:10:03PM +1200, Evan Hanson wrote:
> Hi Peter,
>
> On 2017-05-07 21:45, Peter Bex wrote:
> > The core-library-reorganization page has "(chicken condition)" under
> > "undecided", but I think it's fine the way it is. The attached patches
> > add this module.
>
> These
