Re: 1.5.6: (bound? ) missing from optargs.scm

[Steve Tell]

On Thu, 28 Mar 2002, Thien-Thi Nguyen wrote:

> 2001-05-10  Marius Vollmer  <address@hidden>
> 
>       * optargs.scm (bound?): Removed.  We should not play games with
>       the magical undefined value.
> 
> i don't particularly understand what kinds of games are no longer being
> played, nor what is the suggested way to achieve prior functionality.
> "doc bug" means some kind of blurb explaining these things is due in
> NEWS.

That helps a little.  After a little thought I found an obvious
workaround, using the default-value facility.  That brings up the
question: with this change, when will it ever be useful to _not_ provide a
default value for a keyword or optional argument to a procedure built with
lambda*?

I suppose I can see how a "magical undefined value" could be a bit too
much like perl's "undef" for the purists, but this does make
lambda*/define* less useful IMHO.

Anyway, I am now successfuly building on 1.4 and 1.5.6, with 1.3.4 testing
still remaining.  I feel like I have to support 1.3.4 until more of the
major linux distributions start shipping with 1.4 or later.

Steve

 

--
Steve Tell  address@hidden