unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: patch: (read "\x1b") => #\esc
Date: Tue, 11 Nov 2003 09:18:52 +1000	[thread overview]
Message-ID: <87fzgvrew3.fsf@zip.com.au> (raw)
In-Reply-To: <m3oevjong2.fsf@multivac.cwru.edu> (Paul Jarc's message of "Mon, 10 Nov 2003 17:41:59 -0500")

prj@po.cwru.edu (Paul Jarc) writes:
>
> +	      case EOF:
> +		goto str_eof;

Currently that gets noticed next time around the loop does it?

(But not expecting scm_getc to return EOF a second time is probably a
good thing.)


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2003-11-10 23:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 22:41 patch: (read "\x1b") => #\esc Paul Jarc
2003-11-10 22:48 ` Paul Jarc
2003-11-10 23:18 ` Kevin Ryde [this message]
2003-11-11  2:45   ` Paul Jarc
2003-11-11 21:48     ` Kevin Ryde
2003-11-13 20:10 ` Marius Vollmer
2003-11-18 20:04   ` Paul Jarc
2003-11-19  0:24     ` Paul Jarc
2003-11-29 23:43     ` Marius Vollmer
2003-11-25 17:12   ` Paul Jarc
2003-11-30  1:05     ` 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=87fzgvrew3.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).