Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You plugged a memory leak and that makes it a version 2.0? Gee, I don't really care how many years it has taken, but that seems to me like a too big a version jump, regardless.
    • Isn't that really up to him? He could have changed the version to 5 if he wanted to.
      • Or 6. That seems to be very popular with Microsoft. Sun, with Java, also pulls weird stunts in regard to version numbers. They've lost me on the way.

        Most Perl modules never even make it to version 1.00, not even after years and lots of heavy use. Win32::API for example.
      • Anyway, when a module version jumps from version 1.x to version 2.0, I've come to expect something more than a bug fix.
        • So the doubled performance and code cleanups don’t do it for you?

          And in any case, why would you care? Are you a heavy user of Text::Metaphone or something?

    • You can read my philosophy of version numbers elsewhere. [perl.org]

      Now, as to why I decided this release is version 2.00 can be found in the Changes log.

      Heh, what happened to 1.00? Never existed, it was supposed to be the gamma
      release of the pure perl version of the module. Skipped straight to 1.90,
      alpha XS version.

      1.00 would have been what I considered the "stable" Perl version but I decided to rewrite everything so I jumped over 1.00 directly to 1.9x to symbolize the big change leading up to a "stable" XS version