From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: rlb@defaultvalue.org, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: Items blocking release 1.6.1 (2002-04-21)
Date: 23 Apr 2002 20:16:20 +0200 [thread overview]
Message-ID: <87wuuyl1qj.fsf@zagadka.ping.de> (raw)
In-Reply-To: <E16zk3n-00006F-00@giblet>
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> Ok, I'll looker closer into this, and I now have to say that we can't
> 'fix' it. We would be changing the default default value from '#f'
> to something else. That would be an unacceptable interface change.
>
> but removing `bound?' is acceptable?
Yes. The way the old 'bound?' was implemented was a bug. The mistake
(my mistake) back then was to fix this bug in a sub-optimal way, by
just removing the functionality. Now it is too late to change it
again; and changing it would be quite gratuitous, too.
Using #f as the default default value is a sensible thing, I'd say,
and should even be recommended. From a robustness standpoint,
distinguishing between explicitely specifying a keyword with its
default value in a function call, and not specifying it, should not be
done. That is, it is better to say "When you don't specify the :foo
keyword, it's value is defaulted to #f. A value of #f means bla."
instead of "When you don't specify the :foo keyword, it means bla."
> Since it is easy for the user to provide the functionality on its
> own, we can just leave it as it is.
>
> to provide out of band info, you can use out of band methods (in fact,
> this is the fix i thought you were going to consider).
Yes, but we would have to change the semantics of (ice-9 optargs) in a
way that could lead to silent failures. Removing 'bound?' did not do
that.
> cc'ing guile-user to see who complains (besides me). maybe someone can
> send a patch to do a clean fix, and explain it. maybe it's time to fork
> guile (again).
I think it would be smarter to just fork (ice-9 optargs), if you can
make such fine distinctions.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-23 18:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 20:05 Items blocking release 1.6.1 (2002-04-21) Thien-Thi Nguyen
2002-04-22 20:15 ` Rob Browning
2002-04-22 20:52 ` Thien-Thi Nguyen
2002-04-22 21:12 ` Rob Browning
2002-04-22 21:25 ` Rob Browning
2002-04-22 21:30 ` Rob Browning
2002-04-22 21:51 ` Thien-Thi Nguyen
2002-04-22 23:03 ` Rob Browning
2002-04-22 20:29 ` Bill Gribble
2002-04-22 21:20 ` Thien-Thi Nguyen
2002-04-23 18:16 ` Marius Vollmer [this message]
2002-04-25 9:09 ` tomas
2002-04-25 10:02 ` rm
2002-04-28 16:00 ` Marius Vollmer
2002-04-28 20:27 ` Thien-Thi Nguyen
2002-05-07 18:43 ` Marius Vollmer
2002-04-28 15:58 ` Marius Vollmer
2002-04-28 20:38 ` spu
-- strict thread matches above, loose matches on Subject: below --
2002-04-21 16:22 Rob Browning
2002-04-22 8:35 ` Thien-Thi Nguyen
2002-04-22 13:02 ` Rob Browning
2002-04-22 18:04 ` Marius Vollmer
2002-04-22 18:26 ` Rob Browning
2002-04-22 18:44 ` Marius Vollmer
2002-04-22 18:56 ` Rob Browning
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=87wuuyl1qj.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=rlb@defaultvalue.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).