From: Richard Shann <richard.shann@virgin.net>
To: guile-user@gnu.org
Subject: Re: scm_defined_p(sym, env)
Date: Wed, 24 Aug 2011 21:25:21 +0100 [thread overview]
Message-ID: <1314217521.2295.5.camel@debian2.myhost> (raw)
In-Reply-To: <mailman.191.1314201660.28460.guile-user@gnu.org>
Thanks for this, I see there is also scm_is_true to take care of the
possibility that SCM_BOOL_T might not be a scalar type, we should be
using that too.
Richard
On Wed, 2011-08-24 at 12:01 -0400, guile-user-request@gnu.org wrote:
>
> Richard Shann <richard.shann@virgin.net> writes:
>
> > I didn't find the SCM_UNBNDP() that you mention but since mailing
> the
> > list I stumbled on SCM_UNDEFINED and tried
> > if(opt==SCM_UNDEFINED) ...
> > and that seems to work.
> >
> IIRC, that this works is not actually guaranteed (it depends on the
> type
> of the SCM values; that type might not have defined/reasonable
> behavior
> wrt. the "==" operator, so the right way to write the above comparison
> would be `scm_is_eq(opt, SCM_UNDEFINED)', and incidentially, this is
> how
> SCM_UNBNDP() is defined (see libguile/tags.h, at least on Guile 2.0).
>
> > So (unless I am doing something bad) I think I am back on course -
> > thanks!
> >
> The idiom you used may work for you now, but may be broken at any
> time,
> or even when compiling Guile with a different configuration (search
> for
> SCM_DEBUG_TYPING_STRICTNESS in libguile/tags.h for illustration).
>
> HTH, Rotty
next parent reply other threads:[~2011-08-24 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.191.1314201660.28460.guile-user@gnu.org>
2011-08-24 20:25 ` Richard Shann [this message]
2011-08-23 11:36 scm_defined_p(sym, env) Richard Shann
2011-08-23 11:54 ` rm
2011-08-23 13:26 ` Richard Shann
2011-08-23 19:07 ` Andreas Rottmann
2011-08-29 11:30 ` rixed
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=1314217521.2295.5.camel@debian2.myhost \
--to=richard.shann@virgin.net \
--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).