5.004 vs. LWP: a flag-day?
Randal Schwartz (merlyn@stonehenge.com)
10 Jan 1997 08:56:30 -0700
This is an advance warning of an imminent trouble spot.
Version 5.05 of LWP is incompatible with the soon-to-be-released Perl
5.004, because of %OVERLOAD in URI::URL. Thus, many people will be
forced to stay at Perl 5.003 until a compatible version of LWP is
released.
However, the quick testing I've done on my 5.05 LWP shows that I cannot
get a patched 5.05 to work with the *old* Perl 5.003.
Unless I'm wrong (and I hope I am), this means that the world must
upgrade Perl to 5.004 and and LWP to 5.06(?) *simultaneously*.
Ugh. I hate flag days.
Has anyone else in the intersection of P5P and LWP been looking into
this? Are my fears unfounded? Am I just nuts? :-)
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@ora.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
se) a file that couldn't be found
in any of the libraries mentioned in @INC. Perhaps you need to set
the PERL5LIB environment variable to say where the extra library is,
or maybe the script needs to add the library name to @INC. Or maybe
you just misspelled the name of the file. See perlfunc/require.
gummo%
Here are the versions of LWP I'm using:
# $Id: Request.pm,v 1.17 1996/09/18 12:15:16 aas Exp $
# $Id: UserAgent.pm,v 1.39 1996/12/04 15:24:29 aas Exp $
Changing the URL I'm retrieving makes no difference...
Rohan.
ro11@cornell.edu