> What is lousy and expectation-violating about a keyword argument
> doing what it name describes?
well, this should have been discussed at the R6RS committee, but...
an API is facilitating efficient reading comprehension when the "verbs" are
closer to the beginning of the "sentence" (the sexp)
>it's a tangential, but namely, when #:unwind #t then the handler in a w-e-h
>returns from the w-e-h block, but with #:unwind #f it tries to return to the
>RAISE that raised the condition. i.e. a lousy little keyword arg (usually a
>page down) fundamentally changes the behavior of w-e-h. yet ano
apparently this has been fixed between 3.0.9 and HEAD. i've wasted my time
chasing a ghost...
can we please have a new release? :)
as a sidenote, i also had some broken expectations in my test.scm.
it's a tangential, but namely, when #:unwind #t then the handler in a w-e-h
returns from the w-e
