From: Steve Tell <tell@telltronics.org>
Cc: guile-user@gnu.org
Subject: Re: 1.5.6: (bound? ) missing from optargs.scm
Date: Fri, 29 Mar 2002 01:40:57 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.21.0203290059400.11739-100000@ariel.lan.telltronics.org> (raw)
In-Reply-To: <E16qjNd-0000HF-00@giblet>
On Thu, 28 Mar 2002, Thien-Thi Nguyen wrote:
> 2001-05-10 Marius Vollmer <mvo@zagadka.ping.de>
>
> * 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 tell@telltronics.org
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-03-29 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 6:30 1.5.6: (bound? ) missing from optargs.scm Steve Tell
2002-03-28 8:52 ` Thien-Thi Nguyen
2002-03-28 23:32 ` Thien-Thi Nguyen
2002-03-29 6:40 ` Steve Tell [this message]
2002-03-29 7:44 ` Thien-Thi Nguyen
2002-03-30 2:26 ` Steve Tell
2002-03-30 4:42 ` Thien-Thi Nguyen
2002-03-31 22:06 ` Marius Vollmer
2002-04-01 1:42 ` Thien-Thi Nguyen
2002-03-31 22:46 ` Marius Vollmer
2002-04-24 17:52 ` Marius Vollmer
2002-03-31 22:59 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0203290059400.11739-100000@ariel.lan.telltronics.org \
--to=tell@telltronics.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).