in reply to Activestate 5.8.2 broke my threads :(

Did you report it to ActiveState? You should go ahead and do that.

I have compiled my own win32 ActiveState compatible perl-5.8.2 , and the code runs just fine.

To see how ActivePerl-5.8.2 differs from per-5.8.2 check out http://downloads.activestate.com/ActivePerl/src/5.8/AP808_diff.txt

A lot of the edits are completely benign, but some changes I just cannot understand (if they were improving perl, i'm sure the p5p would've accepted patches).

It's one of the reasons I've stopped installing ActivePerl.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Did you report it to ActiveState?
by ysth (Canon) on Dec 22, 2003 at 08:24 UTC
    Most of that diff seems to be post-5.8.2 patches that AS apparently deemed benign enough to include. Were there particular changes that you questioned?
[reply]
      That is what I question (post release patches AS deemed benign enough to include). It's not the first time that AS in their "quest" to improve their release has introduced bugs (like in this case), that would've been worked out in the normal release cycle.

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
Quit using ActiveState?
by Anonymous Monk on Dec 22, 2003 at 21:47 UTC
    It's one of the reasons I've stopped installing ActivePerl.
    You've quit using AS - what are some of the other reasons?

    Do you build your own perl or do you use another build (ie Apache's build)?

[reply]
      Like I said, I compile my own. The so called "Apache's" build is just ActivePerl.

      Some other reasons i've stopped using AS include actions such as purposely removing pod from their modules, for example ActivePerl::DocTools (inspired me to write Pod::Master), among others. I don't know why they did that, I just know I don't like it :)

      Another reason is the "ActiveState Community License". Perl is released under the Artistic License or the GNU General Public License. I'm no expert, but whatever they were trying to accomplish with their "community license" does not look right to me, and I just don't like it (for one thing, if you type `perl -V', it makes no mention of their community license).

      That's pretty much it, well, that's what I can remember (*mumble* various bugs with PPM...and PerlScript security issues... don't ask me).

      Another reasons is that since I got a compiler I got kind of compile-happy .. I started smoking perl... this weighed heavily on my decision not to use ActivePerl.

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]

In Section Seekers of Perl Wisdom