unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "mikael@djurfeldt.com" <mikael@djurfeldt.com>,
	Adam Faiz <adam.faiz@disroot.org>,
	 guile-devel <guile-devel@gnu.org>,
	Ricardo Wurmus <rekado@elephly.net>, Tomas Volf <~@wolfsden.cz>
Subject: Re: [PATCH] test-suite: Add tests for `for-rdelim-in-port`-related functions.
Date: Fri, 20 Dec 2024 23:30:23 +0900	[thread overview]
Message-ID: <CAPjoZofJ3riCqgJRY7ECR6NHCBjJJd=cD+6ScRLoBUqHVBzJxQ@mail.gmail.com> (raw)
In-Reply-To: <20241220151837.r2Jc2D00o2kJuzj012JdDJ@laurent.telenet-ops.be>

[-- Attachment #1: Type: text/plain, Size: 2760 bytes --]

As I said, I didn't against any of your opinions. But I have my freedom to
comment on what I think important.

So I made my proposal accordingly to the specific issue as you pointed out.
This may not be accepted by you, but that's your freedom to share your mind
further. And I unnecessarily need to respond to it unless I think it's
worth. In case you thought people may misunderstand you, I also care if the
image in your mind is not what showed in your mind. I keep my comments
before anyone show the related code as you described.

But let me emphasize it, this doesn't mean anyone is forced to reimplement
the code. At least I accept the current implementation. Don't forget, these
patches included your efforts either, and I respect that part too, in the
name of the code. Personally, I would like to comment on the existing code
rather than mind.

This thread is not only you and me. Many others are reading it. You don't
need to persuade me. You just claim your mind directly, and wait for folks
agree it, or at least part of it.
Best regards.

On Fri, Dec 20, 2024, 23:18 Maxime Devos <maximedevos@telenet.be> wrote:

> >Here are the "back to the track" reply for folks in this thread.
>
> >
>
> >So the situation is more clear now. The newline in various OS need to
> respectively tested. And my idea is to check OS via (uname) in test cases.
>
> >Now that it's in tests, I think we don't have to talk much about the
> efficiency issue for this specific case.
>
>
>
> No. See what I wrote previously about the subject, and note that most of
> it is independent of whether it’s for testing or not. As you previously
> said you intentionally did not read (parts of) the messages, I’m not going
> to repeat it for you.
>
>
>
> In addition: why not simply _*read*_ the implementation of (ice-9 rdelim)
> to see what platform-detecting mechanism it uses (if any) and reuse that,
> instead of reinventing the wheel? Sounds like it would save effort and
> time, which you seem particularly interested in, and claimed effort/time is
> one of your own arguments against generalisation.
>
>
>
> Also, it doesn’t need to be tested, since read-line is not what’s being
> added or modified here. (Tests for that may be good, but that’s off-topic,
> which you are rather against, and is your most coherent argument against
> generalisation.) Rather, either the used newline in the test needs to be
> adjusted per-platform, or the documentation of read-line needs to be
> adjusted to that \n is always a newline.
>
>
>
> Also, it’s also not a proper “back to the track” reply, since it ignores
> the ‘generalisation’ component of the track.
>
>
>
> Regards,
>
> Maxime Devos
>

[-- Attachment #2: Type: text/html, Size: 4218 bytes --]

  reply	other threads:[~2024-12-20 14:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 15:21 [PATCH 1/2] rdelim: Add new procedure `for-rdelim-in-port` Adam Faiz
2024-12-16 15:24 ` [PATCH 2/2] doc: Add documentation for `for-rdelim-in-port` and, related procedures Adam Faiz
2024-12-17  4:31   ` [PATCH] test-suite: Add tests for `for-rdelim-in-port`-related functions Adam Faiz
2024-12-17  5:11     ` Nala Ginrut
2024-12-17  7:21       ` Mikael Djurfeldt
2024-12-17 16:43         ` Mikael Djurfeldt
2024-12-20  9:15           ` Maxime Devos
2024-12-20  9:57             ` Nala Ginrut
2024-12-20 11:51               ` Maxime Devos
2024-12-20 12:00                 ` Nala Ginrut
2024-12-20 12:53                   ` Maxime Devos
2024-12-20 13:00                     ` Nala Ginrut
2024-12-20 13:45                       ` Maxime Devos
2024-12-20 13:52                         ` Nala Ginrut
2024-12-20 14:18                           ` Maxime Devos
2024-12-20 14:30                             ` Nala Ginrut [this message]
2024-12-20 14:32                               ` Nala Ginrut
2024-12-20 14:47                               ` Maxime Devos
2024-12-20 14:56                                 ` Nala Ginrut
2024-12-20 15:07                                   ` Maxime Devos
2024-12-20 15:13                                     ` Nala Ginrut
2024-12-19 21:50     ` Mikael Djurfeldt
2024-12-20 15:15       ` [PATCH] test-suite: Add tests for `for-rdelim-in-port`-relatedfunctions Maxime Devos
2024-12-20 17:11         ` Mikael Djurfeldt
2024-12-20 17:31           ` Nala Ginrut
2024-12-20 18:40           ` Maxime Devos
2024-12-16 16:46 ` [PATCH 1/2] rdelim: Add new procedure `for-rdelim-in-port` Nala Ginrut

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='CAPjoZofJ3riCqgJRY7ECR6NHCBjJJd=cD+6ScRLoBUqHVBzJxQ@mail.gmail.com' \
    --to=nalaginrut@gmail.com \
    --cc=adam.faiz@disroot.org \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=mikael@djurfeldt.com \
    --cc=rekado@elephly.net \
    --cc=~@wolfsden.cz \
    /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).