[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
This page is part of the web mail archives of SRFI discuss from before July 7th, 2015. The new archives for SRFI discuss contain all messages, not just those from before July 7th, 2015.
On Thursday, June 12, 2003, at 09:03 AM, Felix Winkelmann wrote:
SRFI 39 seems to have some problems (e.g., the name 'parameter,' stuff
Is the SRFI process somewhat "stalled"? There are several
draft SRFI's *way* over the draft period, and I wonder
what is going to happen now.
I find this disappointing. I think the SRFI authors should
show a little bit more commitment.
P.S. Yes, I'm a very impatient person... ;-)
the 'dynamic environment,' et cetera), but the discussion just petered
needs to be revived.
I'm not sure what to think of SRFI 42, Eager Comprehensions. I like
but I don't know how it will fit in with a standard collection API (not
reference to SRFI 44, but see below).
I think SRFI 33 is almost ready to be finalized, but people are just
or something about it.
I don't, however, think SRFI 32 should be finalized, or, in fact, any
collection SRFIs -- sorting, streams, vectors, or general collections.
we need to find some far more general collection library (and ditch
SRFIs 1 and
13, too). SRFI 44 comes somewhat near that, as does a SRFI in
('Scheme Template Library,' as posted on c.l.scheme a few weeks ago),
44 is definitely nowhere near completion (I haven't finished its
implementation, and Scott hasn't done much, as far as I've seen,
a new draft that's far more functional (so I'd have to toss any
implementation I'd written so far, anyways)), and SRFI 45(?) would be
generalized with a real module system in the style of SML.
I know a module system is going to be very controversial, but the
be ignored any longer.