Adam Kennedy wrote:
Yes, the point i was making is that it should treat '0.23_04' as 0.2304.
Actually, that would be wrong. Perl version already have a mapping system.
0.2304 would be 0.230.400, or shorthand, 0.23.4
Underscores are not part of that.
No that's not correct; you do not
On Jun 21, 2006, at 4:23 AM, demerphq wrote:
I see no reason nto to suppress it for $VERSION, but only when the non
alpha char is an underbar.
The point is that suppressing the warning would leave people with
silently broken code. It's telling you that it's treating '0.23_04'
as the
On 6/20/06, Ken Williams [EMAIL PROTECTED] wrote:
On Jun 19, 2006, at 6:37 PM, Ron Savage wrote:
On Mon, 19 Jun 2006 14:32:10 +0200, demerphq wrote:
Hi demerphq
Nope. If you upgrade it should go in to site/lib, meaning you have
to use UNINST=1 if you upgrade.
Are you sure it'll go into
demerphq wrote:
Sorry, do i understand you correctly: Blead is already special cased
not to warn in this situation?
Blead doesn't need to special case it: the version code inherently
treats numbers with embedded underscores as alpha versions:
$ LD_LIBRARY_PATH=. ./perl -e '
package stuff;
demerphq wrote:
On 6/20/06, John Peacock [EMAIL PROTECTED] wrote:
As you can see, you don't even need to create a version object; it is
the version aware UNIVERSAL::VERSION which performs this magic...
Oh cool. Nice touch!
I have a patch to blead which will even make the $VERSION scalar be
On Jun 18, 2006, at 10:58 PM, Ron Savage wrote:
On Sun, 18 Jun 2006 22:02:16 -0500, Ken Williams wrote:
Maybe there's some general UNINST-like mechanism for eliminating
duplicate modules in people's installations when some CPAN module
goes core? I've never heard of this problem, nor its
On Jun 19, 2006, at 6:37 PM, Ron Savage wrote:
On Mon, 19 Jun 2006 14:32:10 +0200, demerphq wrote:
Hi demerphq
Nope. If you upgrade it should go in to site/lib, meaning you have
to use UNINST=1 if you upgrade.
Are you sure it'll go into site/lib?
We may be confusing the two kinds of
On Mon, 19 Jun 2006 20:18:28 -0500, Ken Williams wrote:
Hi Ken
We may be confusing the two kinds of upgrades - upgrading perl from
I suspect that's part of it - but not for me. My policy is to never do an in
situ upgrade of Perl. And yes, that does mean reinstalling all modules I've
On Jun 19, 2006, at 18:55, Ron Savage wrote:
That's why I use a program to install as many of them as can be
automated, and more code to scan the log looking for failures...
What do those programs look like? I wouldn't mind seeing them.
Best,
David
On Jun 18, 2006, at 7:59 PM, Ron Savage wrote:
Hi Folks
Just wondering.
When Module::Build is a core module will it still live in /perl/
site/lib/Module/
or will it move to /perl/lib/Module/?
You're talking about under Win32, right? I believe it will live in /
perl/lib/Module, along
10 matches
Mail list logo
