From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: P Pareit <pieter.pareit@planetinternet.be>, guile-user@gnu.org
Subject: Re: [guile/scwm] 2nd argument problem to scm_definedp()
Date: 17 Sep 2002 23:50:46 +0200 [thread overview]
Message-ID: <87n0qgi8uh.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87elbsip2c.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Why did we decide not to just have scm_module_lookup return SCM_BOOL_F
> if the variable wasn't defined? That seems more flexible. I think
> there was some reason, but I can't reecall it at the moment. i.e.
The reasoning was, if I remember correctly, that making
scm_module_lookup issue the error message will make that error message
more uniform and it will also make it easier for people to use
scm_module_lookup correctly in the 'usual' situation.
We can have a second function thta behaves differently. That function
should also be able to return non-variables (like the mythical macro
transformers).
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-09-17 21:50 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
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 [this message]
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=87n0qgi8uh.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).