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. -Nilson Santos F. Jr. _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
