develooper Front page | perl.perl5.porters | Postings from August 2001

Re: [PATCH 2 of 3] $] is deprecated - EXTERMINATE, EXTERMINATE, EXTERMINATE

Thread Previous | Thread Next
From:
Philip Newton
Date:
August 23, 2001 22:21
Subject:
Re: [PATCH 2 of 3] $] is deprecated - EXTERMINATE, EXTERMINATE, EXTERMINATE
Message ID:
perl.perl5.porters-42481@nntp.perl.org
On 23 Aug 01, at 11:57, John Peacock wrote:

> Ronald J Kimball wrote:
> > 
> > 1. Is v1.300 equal to v1.196.172?  Yes.  I mean no.  I mean...  What was
> >    the question again?
> 
> Can't help you there.  Since both representations in Unicode are the
> same,

They are? Does that mean Perl can't distinguish between "chr(300)" and 
"chr(196).char(172)"? Or between "\x{12c}" and "\x{c4}\x{ac}" and 
"\xc4\xac"? After all, v-strings are supposed to be just "join '', map 
chr".

I would have thought even if the byte sequence were the same, there 
would have been at *least* the difference "UTF8 on" vs "UTF8 off".

> the version strings will be equivalent.

This would not be such a good idea IMO.

> This should be an unlikely occurance for versions, unless someone is
> using CVS a little too religiously (I changed "d" to "D", I better
> commit ;~).  

Not necessarily. Sometimes numbers are not "just" version numbers -- 
some modules have year numbers in their version, and then there's 
things such as Tk with a version number in the 800s(?). Unlikely?

> Oh, and speaking of CVS, if this all works, you will be able to use
> 
> 	$VERSION = qw$Revision: 1.51 $[1];
> 
> and be sure that v10.10 > v10.9!

Sounds like too much DWIM, but good luck.

Cheers,
Philip
-- 
Philip Newton <Philip.Newton@gmx.net>

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About