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

Thanks for the reply. I suspect you might be right about ppm and ActiveState in this case. I removed the ActiveState version and went to CPAN.

My first attempt was to download and attempt to install the most current version of Mech now out there (1.02). Of course, in an ideal world installing a module would be "no problem", but things never run quite so smoothly for me. I hit a dependency with HTML::Parser (v 3.3) for LWP and I could not get it to 'make'. It appears to need a different compiler; but that's a battle I shall save for another day.

I went back several versions of Mechanize and settled on version .59. Probably since it is such an old version it installed nicely. All of my mech code runs again. And I'm back to square one.

I'm getting different errors, but I can't get any response on my multi-select form. If the documentation on CPAN regarding WWW::Mechanize is any indication, I'm not going to be able to get that to work with this version no matter what I do.

Comment on Re^2: WWW::Mechanize, new version, broken code

Replies are listed 'Best First'.
Re^3: WWW::Mechanize, new version, broken code by jacques (Priest) on Jul 26, 2004 at 14:08 UTC
If I were you, I would just uninstall ActivePerl. Get rid of everything from ActiveState, but keep your programs. Then install Cygwin. Go with their Perl distribution.	[reply]
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]


Don't ask to ask, just ask
	PerlMonks