All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,  git@vger.kernel.org
Subject: Re: [PATCH] CodingGuidelines: update the required Perl version
Date: Thu, 05 Nov 2026 09:42:09 -0800	[thread overview]
Message-ID: <xmqqik2bw4y6.fsf@gitster.g> (raw)
In-Reply-To: <auuxjhaauAQ7Vtjs@fruit.crustytoothpaste.net> (brian m. carlson's message of "Wed, 4 Nov 2026 22:28:30 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> On 2026-11-04 at 19:56:57, Junio C Hamano wrote:
>> Tuomas Ahola <taahol@utu.fi> writes:
>> 
>> > Junio C Hamano <gitster@pobox.com> wrote:
>> >
>> >> Tuomas Ahola <taahol@utu.fi> writes:
>> >> 
>> >> > - - We try to support Perl 5.8.1 and later ("use Perl 5.008001").
>> >> > + - We try to support Perl 5.26.0 and later ("use Perl 5.026000").
>> >> 
>> >> Is this in line with what 702d8c1f3b did?  Shouldn't we say
>> >> 
>> >> > + - We try to support Perl 5.26.0 and later ("require v5.26").
>> >> 
>> >> "require v5.26" instead?
>> ...
>> It looks to me that the "parenthetical" you called was designed to
>> be useful by telling you what to have near the top of your Perl
>> source files.  Replacing it with "require v5.26" is exactly in line
>> with that, I would think.
>
> As mentioned above, you want `require`, not `use`, with Perl versions.
> The latter enables the relevant features, which include Unicode strings
> as of 5.12, and that will change the behaviour of our code in ways we're
> probably not expecting.  That didn't happen in 5.8.1 because features
> didn't exist, so the `use` for that version was okay.
>
> You effectively always want `require v5.26` or something equivalent such
> as `require 5.026` in our codebase.  The former is nicer to read,
> though.

Thanks.  Let's see the final version that can immediately be marked
as ready for 'next' then.


  reply	other threads:[~2026-11-05 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01 18:58 [PATCH] CodingGuidelines: update the required Perl version Tuomas Ahola
2026-11-02  4:08 ` Junio C Hamano
2026-11-04 19:34   ` Tuomas Ahola
2026-11-04 19:56     ` Junio C Hamano
2026-11-04 22:28       ` brian m. carlson
2026-11-05 17:42         ` Junio C Hamano [this message]
2026-11-02  6:41 ` Junio C Hamano
2026-11-04 18:59   ` Junio C Hamano
2026-11-05 18:39 ` [PATCH v2] " Tuomas Ahola
2026-11-05 18:45   ` Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqik2bw4y6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    --cc=taahol@utu.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.