From: Andy Wingo <wingo@pobox.com>
To: Torstein Winterseth <kvikende@fsfe.org>
Cc: bug-guile@gnu.org
Subject: Re: Guile v. 2.0.1 does not handle escaped open parentheses correctly.
Date: Mon, 16 May 2011 23:57:41 +0200 [thread overview]
Message-ID: <m362pab962.fsf@unquote.localdomain> (raw)
In-Reply-To: <BANLkTiksmGhZHr0rNNuygrr7Rsnhea=ghA@mail.gmail.com> (Torstein Winterseth's message of "Wed, 11 May 2011 16:22:28 +0200")
Hi Torstein,
On Wed 11 May 2011 16:22, Torstein Winterseth <kvikende@fsfe.org> writes:
> (define bug
> '(\())
AFAIU, \ is not actually an escaping marker in R5RS. The meaning of
your program is not defined by the R5RS, as an initial \ character on a
form is not specified. Guile treats this the same as:
However...
$ guile
scheme@(guile-user)> '\(
$1 = \
scheme@(guile-user)> 1
... )
<unnamed port>:0:0: In procedure #<procedure 18d0500 at <current input>:1:0 ()>:
<unnamed port>:0:0: Wrong type to apply: 1
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]>
Not sure why it decided that it should display a prompt after the first
case; probably a bug somewhere...
But, your assumption is not correct, so this is not a bug, AFAIK. R6RS
does specify an escaping syntax, however, though it is not the one you
are assuming.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-16 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 14:22 Guile v. 2.0.1 does not handle escaped open parentheses correctly Torstein Winterseth
2011-05-16 21:57 ` Andy Wingo [this message]
2011-06-11 17:23 ` Ian Price
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=m362pab962.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=kvikende@fsfe.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).