Nilson Santos Figueiredo Junior wrote:
> On 6/30/06, Christopher H. Laco <[EMAIL PROTECTED]> wrote:
>> Don't do that. Bad things will happen. Always compiled your modules with
>> the same compiler used for the perl install itself on Windows. To that
>> point, you could compile perl in .NET, then do the modules that way too.
>
> FUD.
>
> VS.NET 2003 compiles everything that's compilable successfully for AS Perl.
> That's what I've been using for at least two years without any problems.
>
> As GCC also does compile everything successfully for AS Perl. In fact,
> I don't even know if AS Perl is still compiled using the VC6.
I think that's the point - that AS has switched to gcc and it's *generally*
preferable to use the same compiler as your perl binary was built with.
But I'm still on 5.8.7 until they get a 5.8.8 that doesn't randomly spew
warnings everywhere.
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
