From: Adam Faiz <adam.faiz@disroot.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-devel@gnu.org
Subject: Re: rdelim: Add new procedure `for-line-in-file`.
Date: Mon, 16 Dec 2024 10:29:02 +0800 [thread overview]
Message-ID: <ae34e007-3dc4-e6bf-873d-0d37f37f41e9@disroot.org> (raw)
In-Reply-To: <87ed28kho0.fsf@elephly.net>
Hi Ricardo,
On 12/16/24 00:57, Ricardo Wurmus wrote:
> Hi Adam,
>
> has this patch been discussed somewhere else? I'm asking because I have
> no context other than this patch.
No, actually. Was I supposed to discuss it's use in the patch cover letter?
The reason I sent this patch was to make it convenient for other Scheme
programmers to do per-line processing of a text file, if they need to do so.
>> From 18485a2b94595ae2239f5dcdeb06d3a80bb04bf1 Mon Sep 17 00:00:00 2001
>> From: AwesomeAdam54321 <adam.faiz@disroot.org>
>> Date: Sun, 15 Dec 2024 23:48:30 +0800
>> Subject: [PATCH] rdelim: Add new procedure `for-line-in-file`.
>>
>> * module/ice-9/rdelim.scm (for-line-in-file): Add it.
>> ---
>> module/ice-9/rdelim.scm | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/module/ice-9/rdelim.scm b/module/ice-9/rdelim.scm
>> index d2cd081d7..ffa38efad 100644
>> --- a/module/ice-9/rdelim.scm
>> +++ b/module/ice-9/rdelim.scm
>> @@ -206,3 +206,15 @@ characters to read. By default, there is no limit."
>> line)
>> (else
>> (error "unexpected handle-delim value: " handle-delim)))))
>> +
>> +;;; for-line-in-file [PORT BODY] calls BODY (a procedure with the
>> +;;; line from PORT as it's argument) for every line until the
>> +;;; eof-object is reached. The line provided to BODY is guaranteed
>> +;;; to be a string.
>> +
>> +(define (for-line-in-file file body)
>> + (while #t
>> + (let ((line (read-line file)))
>> + (if (string? line)
>> + (body line)
>> + (break)))))
> It is preferrable to use a docstring instead of a comment. The choice
> of argument names is inconsistent, though. You're using PORT in the
> comment and FILE in the definition. BODY as a name for a procedure is
> also a rather "inspired" choice.
Thanks for the feedback! I'll send a revised patch that addresses these issues.
> Where is BREAK defined?
Break is defined by the ‘while’ loop:
https://www.gnu.org/software/guile/manual/html_node/while-do.html
next prev parent reply other threads:[~2024-12-16 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 16:00 rdelim: Add new procedure `for-line-in-file` Adam Faiz
2024-12-15 16:57 ` Ricardo Wurmus
2024-12-15 20:33 ` Maxime Devos
2024-12-16 2:29 ` Adam Faiz [this message]
2024-12-16 7:42 ` Ricardo Wurmus
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=ae34e007-3dc4-e6bf-873d-0d37f37f41e9@disroot.org \
--to=adam.faiz@disroot.org \
--cc=guile-devel@gnu.org \
--cc=rekado@elephly.net \
/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).