From: Richard Shann <richard.shann@virgin.net>
To: rm@tuxteam.de
Cc: guile-user@gnu.org
Subject: Re: scm_defined_p(sym, env)
Date: Tue, 23 Aug 2011 14:26:31 +0100 [thread overview]
Message-ID: <1314105991.2188.4.camel@debian2.myhost> (raw)
In-Reply-To: <20110823115400.GA596@seid-online.de>
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.
So (unless I am doing something bad) I think I am back on course -
thanks!
Richard
On Tue, 2011-08-23 at 13:54 +0200, rm@tuxteam.de wrote:
> On Tue, Aug 23, 2011 at 12:36:44PM +0100, Richard Shann wrote:
> > I have defined a function with one needed and one optional arg, using
> >
> > scm_c_define_gsubr (name, 2, 0, 0, callback);
> >
> > in my function I need to test if the second argument is present, it
> > looks like I need
> >
> > scm_defined_p(sym, env)
> >
> > but, if so, how do I find the value of env for the top-level
> > environment?
>
> Not shure I understand you here, Richard. Where would sym come from?
> If your function looks like this:
>
> (richards-function required-param an-optional-param)
>
> thane your c function needs exactly two parameters:
>
> ricks_c_func(SCM req, SCM opt) {
>
> ...
>
> if (!SCM_UNBNDP (opt)) {
> /* opt wasn't provided, so do something here */
> }
>
> ...
>
> }
>
>
> Does that help?
>
> Cheers, Ralf Mattes
>
> > Richard Shann
> >
>
> >
next prev parent reply other threads:[~2011-08-23 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2011-08-23 19:07 ` Andreas Rottmann
2011-08-29 11:30 ` rixed
[not found] <mailman.191.1314201660.28460.guile-user@gnu.org>
2011-08-24 20:25 ` Richard Shann
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=1314105991.2188.4.camel@debian2.myhost \
--to=richard.shann@virgin.net \
--cc=guile-user@gnu.org \
--cc=rm@tuxteam.de \
/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).