From: "Mikael Djurfeldt" <mdjurfeldt@gmail.com>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>, guile-devel@gnu.org
Subject: Re: Removal of SCM_UNBOUND
Date: Sun, 16 Apr 2006 00:13:13 +0200 [thread overview]
Message-ID: <66e540fe0604151513h2c0f0290i1d26b1a5977c054c@mail.gmail.com> (raw)
In-Reply-To: <66e540fe0604151506x230ebd10vd6d59fc243ce60b7@mail.gmail.com>
On 4/16/06, Mikael Djurfeldt <mdjurfeldt@gmail.com> wrote:
> On 4/16/06, Mikael Djurfeldt <mdjurfeldt@gmail.com> wrote:
> > (define x (if #f #f))
> > (slot-set! quux 'bar x)
>
> Actually, I notice that I read your post sloppily. SCM_UNDEFINED
> might work, but I think you should check that thoroughly.
While putting together my daugther's Easter egg, I suddenly realized
that the thing that mght bite you is that many parts of GOOPS is
written in Scheme so that, if this UNBOUND value is eqv? to
SCM_UNDEFINED, things go wrong as soon as any Scheme primitive, used
by GOOPS itself, happen to get this value passed in an optional
argument.
I think there *are* instances like this so that making them eqv?
really does introduce a bug. But even if it doesn't right now, having
them eqv? seems likely to introduce future bugs.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-04-15 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 21:41 Removal of SCM_UNBOUND Clinton Ebadi
2006-04-15 22:03 ` Mikael Djurfeldt
2006-04-15 22:06 ` Mikael Djurfeldt
2006-04-15 22:13 ` Mikael Djurfeldt [this message]
2006-04-15 23:26 ` Neil Jerram
2006-04-17 8:21 ` Mikael Djurfeldt
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=66e540fe0604151513h2c0f0290i1d26b1a5977c054c@mail.gmail.com \
--to=mdjurfeldt@gmail.com \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@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).