From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: Items blocking release 1.6.1 (2002-04-21)
Date: 28 Apr 2002 17:58:34 +0200 [thread overview]
Message-ID: <87adrnn7bp.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20020425090914.GA19031@www>
tomas@fabula.de writes:
> On Tue, Apr 23, 2002 at 08:16:20PM +0200, Marius Vollmer wrote:
> [...]
> > 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.
>
> As a provider of some functionality I'd sometimes like to be able
> to distinguish between `value was provided' and `value was not
> provided at all'. It'd be perfectly reasonable to agree on a
> value which means `not provided' (like Perl's undef or Pythons
> None): an user providing *such* a value hopefully knows what
> she's doing...
Yes. You can do this easily when defining such a function. I.e.
(define not-provided (cons* 'not-provided))
(define* (foo :optional (bar not-provided))
(if (eq? not-provided bar)
...))
> ...but #f seems to be just wrong, since it's an often-used `logical'
> value.
To me, it seems just right as a default default value...
> Unspecified seems nice for something ``you don't specify'',
> doesn't it? (I know, you were against that on a previous posting).
You might use the 'unspecified value' (which is different from
SCM_UNDEFINED which was used previously) as the value of not-provided
above, but it seems to be too obscure, for my taste. It doesn't feel
right to me to give #<unspecified> any specific meaning.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-28 15:58 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
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 [this message]
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=87adrnn7bp.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.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).