From: Andy Wingo <wingo@pobox.com>
To: bug-guile <bug-guile@gnu.org>
Subject: port-filename documentation incorrect
Date: Mon, 07 Feb 2011 21:41:19 +0100 [thread overview]
Message-ID: <m31v3jinm8.fsf@unquote.localdomain> (raw)
Quoth the docs:
-- Scheme Procedure: port-filename port
-- C Function: scm_port_filename (port)
Return the filename associated with PORT. This function returns
the strings "standard input", "standard output" and "standard
error" when called on the current input, output and error ports
respectively.
PORT must be open, `port-filename' cannot be used once the port is
closed.
But:
scheme@(guile-user)> (port-filename (current-input-port))
$1 = #f
And additionally, when connecting to a --listen socket:
> (port-filename (current-input-port))
$3 = socket
i.e. a symbol, not a string (!).
Andy
--
http://wingolog.org/
next reply other threads:[~2011-02-07 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 20:41 Andy Wingo [this message]
2011-02-08 22:16 ` port-filename documentation incorrect Andy Wingo
2011-02-28 19:55 ` 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=m31v3jinm8.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--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).