Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

Re: Is there a concerted effort to break CPAN for older perl versions to drive support for v7?

by Tux (Canon)
on Jan 20, 2023 at 15:41 UTC ( [id://11149729]=note: print w/replies, xml ) Need Help??


in reply to Is there a concerted effort to break CPAN for older perl versions to drive support for v7?

This medal has two sides. You only look at the backward compat issues. A developer or maintainer can be seriously hindered in two ways:

  • Maintaining backward compatibility preventing use of new features
  • Future compatibility preventing support for older perls

The step you describe here is most likely a stepping stone to implementation of new features that are only possible in 5.12 and up.

If you depend on a module that works FINE on the current (old) perl and does not have a security issue, why do you expect the author of that module to support 13 year old perl builds? Seriously, you are just saying that this old perl is *more* important than current or upcoming builds. What would your argument be to someone complaining that this module does not work on perl-5.37.8 with the features it promotes?

There are numerous reasons to stick to old perls, as there are numerous reasons to require a minimum version in production environments (to me that is 5.014002), and there are also numerous reasons to draw a line and require a minimuum version just to be able to go forward and support the current state of affairs.

For me the coin mostly drops in supporting old perl versions as my modules are quite high in the CPAN river, but I won't rule out that someday, I will also raise the bar to make development easier.

One more addition: stating a minimum version to authors that test their distro on all supported versions means they also need access to that version. Not all developers have 500+ prebuilt perl versions available. Sometimes you can ignore the minimum version and just build with the version you have. Sometimes you cannot.

merged edited addition: If an author states a minimum version, it might be the lowest version he/she has access to for testing. You might get away with an older version, but the author cannot guarantee it. YMMV. Additionally, they author might find a feature compelling enough to require the version it was introduced in. The end-user that still wants to use their module might be able to rewrite those to something supported in the version they want to support (like $a = $b // $c$a = defined $b ? $b : $c;)


Enjoy, Have FUN! H.Merijn
  • Comment on Re: Is there a concerted effort to break CPAN for older perl versions to drive support for v7?
  • Select or Download Code

Replies are listed 'Best First'.
Re^2: Is there a concerted effort to break CPAN for older perl versions to drive support for v7? [on "reap" consideration]
by kcott (Archbishop) on Jan 21, 2023 at 00:09 UTC

    This node has been considered for reaping. The reason given is:

    "earlier duplicate of Re: Is there a concerted effort to break CPAN for older perl versions to drive support for v7? (the second has additional text, so reap this earlier node)"
    • Both nodes have the same opening paragraphs.
    • The node to keep has a final paragraph which starts with "edited addition: ..."
    • The node to reap has a final paragraph which starts with "One more addition: ..."

    Those two final paragraphs are different; one does not simply represent "additional text".

    It would make sense to merge those two different paragraphs into one of the nodes, then reap the other node.

    At this point, I'm not voting "reap" on either node.

    Edit (afterthought): I think the consideration should be removed until the issue I've described is resolved.

    — Ken

Re^2: Is there a concerted effort to break CPAN for older perl versions to drive support for v7?
by Anonymous Monk on Jan 21, 2023 at 09:57 UTC

    I will also raise the bar to make development easier.

    Got a good example(s)? The blog in question made a philosophical stance

      Got a good example(s)?

      Better boolean support in Perl 5.36

      Also:

      The 5.36 bundle enables the signatures feature. Introduced in Perl ver +sion 5.20.0, and modified several times since, the subroutine signatu +res feature is now no longer considered experimental. It is now consi +dered a stable language feature and no longer prints a warning.

      PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
        Boolean LOL. Signatures indeed.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11149729]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (1)
As of 2024-04-16 15:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found