From: Kevin Ryde <user42@zip.com.au>
Subject: cvs read bad # error report
Date: Wed, 12 Mar 2003 10:25:57 +1000 [thread overview]
Message-ID: <87smttxwfe.fsf@zip.com.au> (raw)
In the current cvs build on a recent i386 debian, a file foo.scm
containing
#allow
processed with
guile -s foo.scm
produces
ERROR: In procedure scm_lreadr:
ERROR:
Exception during displaying of error: misc-error
Whereas I hoped to get a report about an invalid "#" form.
Nosing around read.c, I wonder if scm_input_error should be calling
scm_error_scm with the "args" parameter it receives, rather than
always SCM_EOL. It looks like an invalid # calls scm_input_error with
a message string containing a ~S, and an args with the offending
character.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-03-12 0:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87smttxwfe.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).