Re^2: Backward compatible lexical warnings

To be honest, is there really a need to worry about this? Do you have active users who are not upgrading perl, but are upgrading your module?

Upgrading perl to the next stable release means re-testing every single program you have in production, to find out what this release breaks. It's not something an organization does every day.

Downloading the lastest version of a new module is what people do by default. It is something an organization does every day.

I think his concerns are valid.

Comment on Re^2: Backward compatible lexical warnings

Replies are listed 'Best First'.
Re^3: Backward compatible lexical warnings by chromatic (Archbishop) on Aug 30, 2006 at 23:01 UTC
Upgrading perl to the next stable release... There have been ten stable releases of Perl since 5.6.0. I don't believe that anyone who hasn't upgraded to a Perl released this millennium has a serious desire to install the new version of a module.	[reply]
Re^4: Backward compatible lexical warnings by Anonymous Monk on Sep 01, 2006 at 18:07 UTC
I don't believe that anyone who hasn't upgraded to a Perl released this millennium has a serious desire to install the new version of a module. As opposed to some version of Perl released in some other thousand year time period? Was there some Perl release in 1006 that I'm not aware of?	[reply]