From: Cedric Cellier <rixed@happyleptic.org>
To: guile-user@gnu.org
Subject: scm_with_continuation_barrier returning #f on throws ?
Date: Mon, 6 Sep 2010 13:20:07 +0200 [thread overview]
Message-ID: <20100906112007.GA21079@securactive.net> (raw)
Hello !
With guile-1.8.7, scm_with_continuation_barrier does not seam to return
SCM_BOOL_F on error. I did this :
static void *load_file(void *filename)
{
scm_c_primitive_load((char const *)filename);
scm_force_output(scm_current_output_port());
return NULL;
}
...
SCM res = scm_with_guile(load_file, "a_file_that_doesnt_exist");
Thus, scm_c_primitive_load displays an ERROR message and throws out.
But scm_with_guile, ie. the underlying scm_with_continuation_barrier,
returns 0x0.
Is the bug in the doc, in the code or once again in my head ?
next reply other threads:[~2010-09-06 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 11:20 Cedric Cellier [this message]
2010-09-25 14:36 ` scm_with_continuation_barrier returning #f on throws ? Andy Wingo
2010-09-26 5: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=20100906112007.GA21079@securactive.net \
--to=rixed@happyleptic.org \
--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).