From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org, Roland Orre <orre@nada.kth.se>
Subject: Re: String syntax changed?
Date: Tue, 17 Feb 2004 17:11:31 -0500 [thread overview]
Message-ID: <m3smh9uziu.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87brnx9xx4.fsf@zagadka.ping.de> (Marius Vollmer's message of "Tue, 17 Feb 2004 22:52:07 +0100")
Marius Vollmer <mvo@zagadka.de> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> Roland Orre <orre@nada.kth.se> wrote:
>>> (begin (display "$\\scriptstyle{P(A\|D)}$") (newline))
>> ...
>>> ERROR: #<unknown port>:1:38: illegal character in escape sequence: #\|
>>> ABORT: (read-error)
>>> ERROR: Unbound variable: D
>>> ABORT: (unbound-variable)
>>
>> Hm. With different string contents, this could have done something
>> dangerous. I'm not sure what could have been done about it, though.
>
> We could gobble up the rest of the string after detecting an error.
> Any takers?
The problem is that after a syntax error, you don't really know where
the end of the string was supposed to be. And even if you guess right
on that, you're still left in the middle of (begin (display.
Or did you mean the rest of the line? At least interactively, we
could gobble up and discard all input until select()/poll() says there
is no more, or read in non-blobking mode until EAGAIN.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-02-17 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 0:55 String syntax changed? Roland Orre
2004-01-19 3:21 ` Joshua Judson Rosen
2004-01-19 10:24 ` Roland Orre
2004-01-19 4:37 ` Paul Jarc
2004-01-19 5:53 ` Keith Wright
2004-02-17 21:52 ` Marius Vollmer
2004-02-17 22:11 ` Paul Jarc [this message]
2004-02-18 23:38 ` Marius Vollmer
2004-02-19 6:21 ` Paul Jarc
2004-02-23 19:18 ` Marius Vollmer
2004-02-24 22:19 ` Paul Jarc
2004-03-20 23:03 ` Marius Vollmer
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=m3smh9uziu.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-user@gnu.org \
--cc=orre@nada.kth.se \
/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).