From: Julian Graham <joolean@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: r6rs incompatibilities
Date: Sun, 23 May 2010 13:24:29 -0400 [thread overview]
Message-ID: <AANLkTin40a3v1ksCvOXaEFmSia0FDnkd1so0F8h9EaQL@mail.gmail.com> (raw)
In-Reply-To: <983244.37247.qm@web37906.mail.mud.yahoo.com>
Hi Mike,
> What happens with this patch if the file only contains the four
> characters "#!r6" followed by EOF? Does it behave appropriately
> after calling scm_ungetc on EOF? (I guess that would make it an
> unterminated hash bang comment.)
If the fifth character is EOF instead of 'r', control is handed to
scm_read_scsh_block_comment (after ungetting EOF), which raises the
appropriate unterminated comment error.
Regards,
Julian
next prev parent reply other threads:[~2010-05-23 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:54 r6rs incompatibilities Andy Wingo
2010-05-21 12:47 ` Julian Graham
2010-05-21 17:15 ` Andy Wingo
2010-05-23 15:35 ` Julian Graham
2010-05-23 16:02 ` Mike Gran
2010-05-23 17:24 ` Julian Graham [this message]
2010-05-23 20:52 ` Andy Wingo
2010-05-23 21:26 ` Andy Wingo
2010-05-26 13:02 ` Julian Graham
2010-05-26 13:21 ` Andy Wingo
2010-05-26 16:43 ` Ludovic Courtès
2010-05-27 8:06 ` Andy Wingo
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=AANLkTin40a3v1ksCvOXaEFmSia0FDnkd1so0F8h9EaQL@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.com \
--cc=wingo@pobox.com \
/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).