Jeff Black

• Website: www.about.me/jeffblack

Recent Actions

• Commented on On the version number succeeding Perl 5
  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

• Joel Berger commented on On the version number succeeding Perl 5

  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.

• Ether commented on On the version number succeeding Perl 5

  “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… :)

• Ether commented on On the version number succeeding Perl 5

  “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… :)

• Toby Inkster commented on On the version number succeeding Perl 5

  strictures.pm also enables fatal warnings. There are some warnings I’d never want to be switched on by default, let alone fatal by default.

  (I’m thinking mostly of uninitialized, void and once, but also to an extent numeric.)

• Ether commented on On the version number succeeding Perl 5

  I can see not wanting some warnings to be fatal, but it’s so rare to need to disable certain warnings entirely (e.g. numeric) that I’d be firmly on the side of keeping them enabled.

  Another change one could make in such a release is to do all the things tchrist lists as needed for full unicode and utf8 compliance: http://stackoverflow.com/a/6163129/40468