From: Vincent De Groote <vincent.degroote@win.be>
Subject: Newbie question: bind a variable on the fly
Date: Sat, 10 Jun 2006 11:25:44 +0100 [thread overview]
Message-ID: <1149935144.4753.10.camel@encelade-dev3> (raw)
Hello,
Is there a way to catch an "unbound-variable" exception, bind the
variable on the fly, and continue execution as if the exception didn't
occurs ?
I'd like to catch this exception in a c function: the exception context
should be available, to retrieve the variable or function name. This
handler will lookup the value in a relational database.
Is this possible ?
Thanks for you replies
Vincent De Groote
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2006-06-10 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 10:25 Vincent De Groote [this message]
2006-06-10 13:08 ` Newbie question: bind a variable on the fly Marius Vollmer
2006-06-11 17:42 ` Jon Wilson
2006-06-12 22:17 ` Neil Jerram
2006-06-13 18:26 ` Jonathan Wilson
-- strict thread matches above, loose matches on Subject: below --
2006-06-10 10:23 Vincent De Groote
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=1149935144.4753.10.camel@encelade-dev3 \
--to=vincent.degroote@win.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).