Re^3: WWW::Mechanize, new version, broken code

Replies are listed 'Best First'.
Re^4: WWW::Mechanize, new version, broken code by Corion (Patriarch) on Jul 26, 2004 at 14:12 UTC
I'm not exactly sure where you get the idea that running a Perl in an emulator box instead of running the native Perl will be better. Cygwin Perl has slow performance, ugly and weird file names (like the rest of Cygwin), and no proper Win32:: integration - three lacking things that ActiveState provides. If you want to escape the grasp of PPM and PPM3, you can install the (now free) compilers from Microsoft to compile either just the needed extensions or the whole Perl for Win32, but to recommend the ugly crutch of Cygwin as a solution strikes me as odd.	[reply]
Re^5: WWW::Mechanize, new version, broken code by jacques (Priest) on Jul 26, 2004 at 14:19 UTC
Yes, I agree with you on the points you raise. But he was talking about Mech and HTML::Parser. Nothing to do with Win32::integration at all.	[reply]
Re^4: WWW::Mechanize, new version, broken code by WhiteBird (Hermit) on Jul 26, 2004 at 18:24 UTC
I might try that some day. Currently I've got a company Intranet that uses ActiveState 5.6.1 on a Windows environment. I don't have the time to make any drastic changes to that right now. I've got the freedom to do that on my home PC, but I like to keep the environments consistent from home to work because I do a lot of work from home. I'm building a test box, though, and will at least upgrade to a more current Perl version there in the near future. I've not really had any difficulty with ActiveState until recently.	[reply]