Jeff Black

Recent Actions

In lieu of Perl 5.x and Perl 6.x I think converting to a code-name branding would help achieve what you seek. Certainly version numbers would be present, but the public face would be the code-name similar to Android OS versions...

Comment Threads

If incrementing the major version number signifies a breaking change, then by using the year as a major version number you essentially say there will be a “breaking” release each year. Yes incrementing to version 7 would signify a breaking release (as minor as the one I am proposing), but we wouldn’t be saying that 8 is coming the very next year.

“Breaking” backcompat in the sense of disabling certain syntax by default but still allowing it to be used if options are set: fantastic? To no indirect I’d add no bareword::filehandles and no multidimensional.

Wait, isn’t that what use strictures does, which is used by Moo? hmmmm… :)

“Breaking” backcompat in the sense of disabling certain syntax by default but still allowing it to be used if options are set: fantastic! To no indirect I’d add no bareword::filehandles and no multidimensional.

Wait, isn’t that what use strictures does, which is used by Moo? hmmmm… :)

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community.
Written in Perl and offering the modern features you’ve come to
expect in blog platforms, the site is hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.