On Sat, May 03, 2014 at 10:45:04PM -0700, Evan Hanson wrote:
@ -hackers: I think `alist-ref`'s fallback search function should match
the behavior of core's versions. Objections?
I agree. Here's a patch to do that. I've taken the opportunity to get
rid of the square brackets in this
Hi,
+ (assert-error (alist-ref 'foo 'bar cmp))
+ (assert-error (alist-ref 'foo '(bar) cmp)))
What's a good predicate to use to check whether what will be passed to
alist-ref will not throw an exception?
The 2nd assert-error rules out a simple list? or an O(1) algorithm.
(Tho' list? is
Hi,
I've released version 0.4 of the rest-bind egg.
rest-bind Generates wrappers to REST-like HTTP APIs.
0.4 makes the support for APIs that have constant path-fragments after
the arguments generally available. This has been sitting in trunk since
last July and no one seems to have had any
Hi,
I've released version 0.2 of the spiffy-cgi-handlers egg.
spiffy-cgi-handlers adds support to spiffy for CGI and derivatives
(currently only FastCGI).
0.2 adds support to fcgi-handler (the module that provides FastCGI
support) for the non-blocking sockets produced by the socket egg in
Hi,
I am not an expert here, but I find these functions ill-defined.
Both take as input a time-vector which already carries the timezone
information (seconds west of UTC). So a time-seconds function just
seems the right thing to me. Having to specify the local/utc prefix
feels redundant,
On Sun, May 04, 2014 at 01:52:06PM +0100, Andy Bennett wrote:
Hi,
+ (assert-error (alist-ref 'foo 'bar cmp))
+ (assert-error (alist-ref 'foo '(bar) cmp)))
What's a good predicate to use to check whether what will be passed to
alist-ref will not throw an exception?
I don't understand
Andy Bennett scripsit:
We also had to fix the dropbox egg where it calls alist-ref. Some time
after CHICKEN 4.7.0 it became mandatory to pass a well formed alist to
alist-ref but we were relying on it returning the default value.
For the record, it is an error in all versions of Scheme to
Peter Bex scripsit:
What's a good predicate to use to check whether what will be passed to
alist-ref will not throw an exception?
I don't understand the question.
See the post I just sent for such a predicate.
No, the check only checks while it's cdring down the list, so it will
only
On Sun, May 04, 2014 at 03:00:52PM -0400, John Cowan wrote:
Peter Bex scripsit:
What's a good predicate to use to check whether what will be passed to
alist-ref will not throw an exception?
I don't understand the question.
See the post I just sent for such a predicate.
Thanks.
