|
From: | Stephen Compall |
Subject: | Re: srfi-18 requirements |
Date: | Mon, 15 Oct 2007 17:35:12 -0500 |
User-agent: | Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 |
Julian Graham wrote:
(SRFI-18 make-condition-variable takes an optional argument that you can use to "name" the condition var). To work around this, I was going to create backup bindings of the original primitives and then refer to them in my scheme reimplementations, a la: (define guile:make-condition-variable make-condition-variable) (define (make-condition-variable . foo) (let ((m (guile:make-condition-variable))) (do-something))) ...and even if the user noticed the slightly different behavior, that would be okay, because she'd specifically requested it by loading (srfi srfi-18).
I can always get those if I want them with (@ (guile) make-condition-variable).
Also, unless there's a type conflict, I think other existing modules simply assume you can deal with more optional arguments than you expect. For example, SRFI-1 adds a third optional argument to assoc, the `=' argument. You can use `#:replace' in define-module to suppress the warning.
-- ;;; Stephen Compall ** http://scompall.nocandysw.com/blog ** "Peta" is Greek for fifth; a petabyte is 10 to the fifth power, as well as fifth in line after kilo, mega, giga, and tera. -- Lee Gomes, performing every Wednesday in his tech column "Portals" on page B1 of The Wall Street Journal
[Prev in Thread] | Current Thread | [Next in Thread] |