From: Ian Price <ianprice90@googlemail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: I/O, modules
Date: Tue, 13 Nov 2012 22:29:23 +0000 [thread overview]
Message-ID: <87lie5t9vg.fsf@googlemail.com> (raw)
In-Reply-To: <87fw4defrq.fsf@tines.lan> (Mark H. Weaver's message of "Tue, 13 Nov 2012 09:31:05 -0500")
Mark H Weaver <mhw@netris.org> writes:
> As shown in the upcase program above, (read-delimited "" port) will read
> the whole file as a string. You need to (use-modules (ice-9 rdelim)) to
> import this procedure.
A perhaps more lucid way is to use get-string-all from (rnrs io ports)
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2012-11-13 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 5:57 I/O, modules thorsopia
2012-11-13 9:31 ` Ludovic Courtès
2012-11-13 9:53 ` Thien-Thi Nguyen
2012-11-13 14:31 ` Mark H Weaver
2012-11-13 14:50 ` Mike Gran
2012-11-13 22:29 ` Ian Price [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-13 11:45 tantalum
2012-11-13 23:03 ` Ian Price
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=87lie5t9vg.fsf@googlemail.com \
--to=ianprice90@googlemail.com \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).