From: Marius Vollmer <mvo@zagadka.de>
Cc: bug-guile@gnu.org
Subject: Re: ice-9 lineio read-char versus unread-string
Date: 03 May 2003 22:26:04 +0200 [thread overview]
Message-ID: <87el3fdbfn.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87he9tn1bv.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> I guess this is just a missing index for the string-ref call in the
> getc handler of make-line-buffering-input-port. Judging by the
> substring taken I guess it should be 0.
Right. Fixed in both branches, although I think the code hasn't
been used for three years or so...
The (ice-9 lineio) module was there to fix a deficiency in the core
ports and the original author expected it to be removed somewhen.
Maybe we should just do that. Anybody?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2003-05-03 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 22:51 ice-9 lineio read-char versus unread-string Kevin Ryde
2003-05-03 20:26 ` Marius Vollmer [this message]
2003-05-05 17:47 ` Neil Jerram
2003-05-13 17:33 ` Marius Vollmer
2003-05-13 17:46 ` Paul Jarc
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=87el3fdbfn.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=bug-guile@gnu.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).