From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Tor Arntsen <tor@spacetec.no>, Tait <git.git@t41t.com>,
git@vger.kernel.org, Alex Riesen <raa.lkml@gmail.com>
Subject: Re: Let's bump the minimum Perl version to 5.8
Date: Fri, 24 Sep 2010 14:04:08 +0000 [thread overview]
Message-ID: <AANLkTikLYjKHyYOqiubygOD6nWO-FUS38dLALnx3iJ_8@mail.gmail.com> (raw)
In-Reply-To: <86pqw3uuba.fsf@red.stonehenge.com>
On Fri, Sep 24, 2010 at 13:47, Randal L. Schwartz <merlyn@stonehenge.com> wrote:
>>>>>> "Ævar" == Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
> Ævar> Since we're not getting patches for common things that have been
> Ævar> broken on 5.6 for years and bumping the requirenment to an 8 year old
> Ævar> perl (5.8) instead of a 10 year old one (5.6) would make things much
> Ævar> easier, including:
>
> Ævar> * Fixing the perl/ Makefile mess
>
> Ævar> * Being able to use 5.8 features
>
> Ævar> * Being able to honestly support the 5.8 release, 5.6 doesn't even
> Ævar> compile on modern systems without undocumented monkeypatches, and
> Ævar> few people use it so we don't get fixes for it.
>
> Ævar> I'd like to propose dropping 5.6 support, and move to say 5.008. I can
> Ævar> do the work required to add appropriate docs / use statements and
> Ævar> fixes to bugs that we can't fix on 5.6.
>
> As the token resident Perl expert, I'd be completely fine with that.
> Sane choice.
>
> It might be useful to document that by adding:
>
> require 5.008;
Right, except that should be `use 5.008`. Since you don't want to run
anything else within an implicit or explicit BEGIN block before perl
fails on that. E.g. `require 5.008; use Digest::MD5;` would just spew
an error about Digest::MD5.
The only reason you'd want `require $version' is if you care about
5.005, but even then you can do `BEGIN { require 5.008 }`.
next prev parent reply other threads:[~2010-09-24 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 12:56 Let's bump the minimum Perl version to 5.8 Ævar Arnfjörð Bjarmason
2010-09-24 13:08 ` Tor Arntsen
2010-09-24 13:32 ` Ævar Arnfjörð Bjarmason
2010-09-24 13:59 ` Andreas Ericsson
2010-09-24 19:10 ` Ævar Arnfjörð Bjarmason
2010-09-26 10:09 ` Andreas Ericsson
2010-09-24 14:08 ` Tor Arntsen
2010-09-24 18:03 ` Brian Gernhardt
2010-09-27 7:59 ` Tom G. Christensen
2010-09-24 17:38 ` Pascal Obry
2010-09-24 19:39 ` Joshua Juran
2010-09-24 13:47 ` Randal L. Schwartz
2010-09-24 14:04 ` Ævar Arnfjörð Bjarmason [this message]
2010-09-24 14:07 ` Randal L. Schwartz
2010-09-24 20:00 ` [PATCH/RFC] perl: bump the required Perl version to 5.8 from 5.6.[21] Ævar Arnfjörð Bjarmason
2010-09-26 10:22 ` Tor Arntsen
2010-09-27 7:36 ` Tom G. Christensen
2010-09-24 20:00 ` [PATCH] perl: use "use warnings" instead of -w Ævar Arnfjörð Bjarmason
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikLYjKHyYOqiubygOD6nWO-FUS38dLALnx3iJ_8@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git.git@t41t.com \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=raa.lkml@gmail.com \
--cc=tor@spacetec.no \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).