From: Mike Gran <spk121@yahoo.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: Need help with catching reader error
Date: Wed, 22 Apr 2009 08:40:17 -0700 [thread overview]
Message-ID: <1240414817.3133.110.camel@localhost.localdomain> (raw)
In-Reply-To: <877i1cspsz.fsf@delenn.lan>
On Wed, 2009-04-22 at 16:53 +0200, Andreas Rottmann wrote:
> Mike Gran <spk121@yahoo.com> writes:
> > (with-test-prefix "basic char handling"
> > (pass-if-exception "non-existent named character"
> > exception:read-error
> > #\foobar))
> >
> You have a syntax error in your source script, which will hence not be
> able to be read and consequently not be able to be evaluated.
>
> Use this instead of #\foobar in the source text:
>
> (with-input-from-string "#\\foobar" read)
>
> This way, your source has legal syntax.
> --Rotty
Nice. It works great. Thanks.
-Mike Gran
next prev parent reply other threads:[~2009-04-22 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 14:32 Need help with catching reader error Mike Gran
2009-04-22 14:53 ` Andreas Rottmann
2009-04-22 15:40 ` Mike Gran [this message]
2009-04-22 20:15 ` Ludovic Courtès
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=1240414817.3133.110.camel@localhost.localdomain \
--to=spk121@yahoo.com \
--cc=a.rottmann@gmx.at \
--cc=guile-devel@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).