From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH v2] Clarify Inline::C dependency (optional on Linux, required elsewhere)
Date: Sat, 02 Sep 2023 21:08:25 +0200 [thread overview]
Message-ID: <20230902210825+0200.747967-stepnem@smrk.net> (raw)
In-Reply-To: <20230902185015.M198704@dcvr>
On Sat, 02 Sep 2023 18:50:15 +0000
Eric Wong wrote:
> Štěpán Němec <stepnem@smrk.net> wrote:
>> -Numerous optional modules are likely to be useful as well:
>> +Numerous other modules are likely to be useful as well:
>
> What is the reasoning for this change?
> "optional" is an important point to state, IMHO.
> Using "other" is more ambiguous, I think.
We've now established that at least Inline::C is not optional on all
systems. Is that really the only case? (I mean, some of the modules
have "optional" again in their respective parentheticals: is that just
redundancy, or does it imply that the others are less optional?) Even
if it _is_ the only case, isn't saying "optional" misleading?
>> @@ -76,8 +76,9 @@ Numerous optional modules are likely to be useful as well:
>> - Inline::C deb: libinline-c-perl
>> pkg: p5-Inline-C
>> rpm: perl-Inline (or perl-Inline-C)
>> - (speeds up process spawning on Linux,
>> - see public-inbox-daemon(8))
>> + (required for lei on *BSD; speeds up process
>> + spawning on Linux, see
>> + public-inbox-daemon(8))
>
> I think breaking up the lines on punctuation improves readability:
>
> (required for lei on *BSD;
> speeds up process spawning on Linux,
> see public-inbox-daemon(8))
That's much better, thank you!
> I particularly dislike having "process" and "spawning"
> being on separate lines.
Yeah, it's horrible, but somehow your sane version didn't occur to me...
Thanks,
Štěpán
next prev parent reply other threads:[~2023-09-02 19:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 5:10 [PATCH 0/7] various build fixes + OpenBSD compat Eric Wong
2023-08-30 5:10 ` [PATCH 1/7] treewide: drop MSG_EOR with AF_UNIX+SOCK_SEQPACKET Eric Wong
2023-08-30 5:10 ` [PATCH 2/7] Makefile.PL: fix syntax for ASan and valgrind targets Eric Wong
2023-08-30 5:10 ` [PATCH 3/7] Makefile.PL: depend on autodie, at least for tests Eric Wong
2023-08-30 5:10 ` [PATCH 4/7] t/kqnotify: improve test reliability on OpenBSD Eric Wong
2023-08-30 5:10 ` [PATCH 5/7] xap_helper.h: don't compress debug sections " Eric Wong
2023-08-30 5:10 ` [PATCH 6/7] xap_helper.h: limit stderr assignment to glibc+FreeBSD Eric Wong
2023-08-30 5:10 ` [PATCH 7/7] xap_helper.h: fix double-free on OpenBSD hdestroy Eric Wong
2023-08-30 12:34 ` [PATCH 0/7] various build fixes + OpenBSD compat, " Štěpán Němec
2023-08-30 21:18 ` Eric Wong
2023-08-31 9:11 ` Štěpán Němec
2023-08-31 17:26 ` Štěpán Němec
2023-09-01 11:09 ` Eric Wong
2023-09-02 10:54 ` Štěpán Němec
2023-09-02 11:07 ` [PATCH v2] Clarify Inline::C dependency (optional on Linux, required elsewhere) Štěpán Němec
2023-09-02 18:50 ` Eric Wong
2023-09-02 19:08 ` Štěpán Němec [this message]
2023-09-02 19:44 ` Eric Wong
2023-09-02 20:45 ` Štěpán Němec
2023-09-02 20:56 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230902210825+0200.747967-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=e@80x24.org \
--cc=meta@public-inbox.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).