fluca1978

Recent Actions

• Commented on blog change... again...
  You are not alone! In the meantime, this could help: https://github.com/blogs-perl-org/blogs.perl.org/issues/291#issuecomment-69999275...
• Commented on The dream of "use 7;"
  While I agree that Perl 5 and 6 are different languages, I strongly disagree that versioning should be parallel. I believe people will get even more confusing of seeing that Perl 5.20.1 is in the future than Perl 6.1.5. The...
• Commented on What prevent warnings pragma become default feature?
  I suspect retro cvompatibility is the issue. If you enable warnings on default you nave to refactor old code to USS no warnings....
• Commented on I want Package BLOCK syntax return 1.
  I guess you assume that every package is going into a separate file, and therefore a module to load. But if you define several packages into the same file unit, you are going to require Perl to conclude each block...

Comment Threads

• Yuki Kimoto commented on What prevent warnings pragma become default feature?

  fluca1978

  >I suspect retro cvompatibility is the issue. If you enable warnings on default you nave to refactor old code to USS no warnings.

  No, No, I insist that "use VERSION" enable warnings pragma by default. retro compatibility is no matter.

  
  

• Luca Ferrari commented on What prevent warnings pragma become default feature?

  If retro compatibility is not an issue, I suspect that Perl developers would have already enabled warnings by default.

  On the same line of thoughts, why is not "my" a default for variables?

  Why not automatically using a predefined set of modules without having to specify "use"?

  The language has been built and evolved in a specific way, so while we can change the future, we cannot destroy the past.

• Yuki Kimoto commented on The dream of "use 7;"

  Toby Inkster

  >Many people who want to be able to increment major versions for Perl have now compromised and decided that the second part of the version number is the major version.

  This is strange thinking in Perl core team. perl is not perl 5 language. perl is perl language.

  perl 1 is perl language. perl 2 is perl language. perl 3 is perl language. perl 4 is perl language. perl 5 is perl language.

  1, 2, 3, 4, 5 is not language name. This is major version number. This is natural thinking in outside of Perl community.

  If this problem is not resolved, o…

• Yuki Kimoto commented on The dream of "use 7;"

  fluca1978

  >This reminds me the numbering of PostgreSQL, where the first digit is the "scope" release, the second number is the major version and the third is the minor one.

  This is OK because PostgreSQL can new scope release. Problem is that Perl never do new scope release.

  Perl 7 is what thing?

  Is Perl 5, Perl 6, Perl 7, Perl8, ... are different language?

  If someone release Perl 7 as Perl 5 successor, who stop it?
  

• Flavio Poletti commented on blog change... again...

  @fluca1978 I'm actually not doing the switch because of any issue with blogs.perl.org - I love the site and I think that the people behind it are amazing.

  I only wanted something supporting a less "online" workflow and the additional customization capabilities are a nice add-on.