From: Rob Browning <rlb@defaultvalue.org>
Cc: P Pareit <pieter.pareit@planetinternet.be>, guile-user@gnu.org
Subject: Re: [guile/scwm] 2nd argument problem to scm_definedp()
Date: Mon, 16 Sep 2002 14:55:03 -0500 [thread overview]
Message-ID: <87lm61ogko.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87sn09lo1i.fsf@zagadka.ping.de> (Marius Vollmer's message of "16 Sep 2002 21:42:01 +0200")
Marius Vollmer <mvo@zagadka.ping.de> writes:
> If you want to default an optional argument from C, use SCM_UNDEFINED:
>
> if (SCM_NFALSEP (scm_definedp (load_path_symbol, SCM_UNDEFINED)))
> ...
>
> I guess you want the default. If not, things get messy. The lexical
> environment that definedp expects is the data structure that gets
> passed as the second argument to macro transformers.
Do we have anything like
scm_defined_in_modulep (sym, module)
If not, should we? (ISTR some discussion about this a while back...)
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-09-16 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 18:49 [guile/scwm] 2nd argument problem to scm_definedp() P Pareit
2002-09-16 19:42 ` Marius Vollmer
2002-09-16 19:55 ` Rob Browning [this message]
2002-09-16 20:24 ` Marius Vollmer
2002-09-17 9:25 ` rm
2002-09-17 21:51 ` Marius Vollmer
2002-09-17 9:25 ` P Pareit
2002-09-17 13:53 ` P Pareit
2002-09-17 21:38 ` Marius Vollmer
2002-09-16 19:49 ` Rob Browning
2002-09-16 19:53 ` Rob Browning
2002-09-16 20:22 ` Marius Vollmer
2002-09-16 20:25 ` Rob Browning
2002-09-17 16:00 ` Rob Browning
2002-09-17 21:50 ` Marius Vollmer
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=87lm61ogko.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-user@gnu.org \
--cc=pieter.pareit@planetinternet.be \
/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).