RE: ActivePerl Build 615 Released

Hmmmm.
Is it really worth it to update to that one?

I am happy with my version of ActivePerl build 522, even if it does not support forking.

And this piece of news, anyway, says that between the last build and the current one is basically more support for Microsoft Web Server... the Evil Land ...

I don't think that I will EVER need PerlScript and ASP, and I do think that people who convert their mind to those new ideas are heretic.

Comment on RE: ActivePerl Build 615 Released

Replies are listed 'Best First'.
RE: RE: ActivePerl Build 615 Released by Corion (Patriarch) on Jul 22, 2000 at 15:33 UTC
If you are using ActiveState Perl Build 613, I strongly recommend that you upgrade, because some serious flaws in the PPM were fixed. On the other side, I'm still using AS Perl Build 522, as `Image::Magick` refuses to work under all newer builds (under Win32), and that's a no-go for me. I'm still waiting for the Unicode stuff to get a bit more stable, but then I'll switch over to Perl 5.6 in the "production" environments, provided that `Image::Magick` works without me having to install, configure and start VC :)	[reply]

Replies are listed 'Best First'.

RE: RE: ActivePerl Build 615 Released
by Corion (Patriarch) on Jul 22, 2000 at 15:33 UTC

If you are using ActiveState Perl Build 613, I strongly recommend that you upgrade, because some serious flaws in the PPM were fixed.

On the other side, I'm still using AS Perl Build 522, as Image::Magick refuses to work under all newer builds (under Win32), and that's a no-go for me.

I'm still waiting for the Unicode stuff to get a bit more stable, but then I'll switch over to Perl 5.6 in the "production" environments, provided that Image::Magick works without me having to install, configure and start VC :)

[reply]