From: "Göran Weinholt" <INVALID.NOREPLY@gnu.org>
To: "Göran Weinholt" <goran@weinholt.se>, bug-guile@gnu.org
Subject: [bug #31766] Missing procedure `port-eof?'
Date: Thu, 25 Nov 2010 11:28:22 +0000 [thread overview]
Message-ID: <20101125-122821.sv2373.10525@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?31766>
Summary: Missing procedure `port-eof?'
Project: Guile
Submitted by: weinholt
Submitted on: Thu Nov 25 12:28:21 2010
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
The R6RS procedure port-eof? is missing.
FWIW, the R6RS support is really shaping up. I've hacked around the missing
port-eof?, missing intraline whitespace support and applied rotty's
rnrs-tweaks.diff. Most of my own test programs run fine now.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31766>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
reply other threads:[~2010-11-25 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101125-122821.sv2373.10525@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=goran@weinholt.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).