----- Original Message -----
From: "KONOVALOV, Vadim (Vadim)** CTR **" <[EMAIL PROTECTED]>
.
.
For one, Strawberry gives you the compiler as part of the
installation. You don't have to go find MinGW, figure out which
packages you need, and so on. It's compiler-enabled right away.
I consider this is a bad feature, that will help lazy programmer in a
short run but its better to bother about C compiler carefully and to not
have uncontrollable number of MinGW everywhere. Perl is resizeable to be
from very small installation to a huge distribution. I don't like perl to
be always huge
I think it's a good thing to be offering the C compiler in the download. I
think it would be even better if that download included the g77 compiler,
and if there was an option to *not* install MinGW (for those who already
have it).
Also, when it first came out, ActiveState was not as friendly to MinGW
AFAIR all was fine with Activeperl with mingw with 5.6.0
But only if you performed some hacks or used ExtUtils::FakeConfig, right ?
I think it's fair enough to say that ActiveState is now more friendly to
MinGW - in that, if you now want to use MinGW with ActivePerl, neither hacks
nor ExtUtils::FakeConfig are needed.
I am happy with CPAN on Activestate's perl throughout all versions I use.
Me, too. Well .... I don't actually use CPAN ... but I'm happy to build
extensions on ActivePerl using MinGW (either with or without
ExtUtils::FakeConfig, as needed).
And I'm happy to build extensions on Strawberry Perl as well.
There's a small number of Win32::* modules that can be built *only* using a
Microsoft Compiler. As it currently stands, those modules can't be built on
Strawberry Perl (unless some significant hacking were to be done). I guess
we'll know that things have come full circle when we see Strawberry Perl
accommodate the use of Microsoft Compilers - in much the same way as
ActivePerl now accommodates the use of MinGW. (In the meantime, I don't
intend to hold my breath :-)
Cheers,
Rob
