Re: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-25 Thread Luke Palmer
On 25 Jul 2002 [EMAIL PROTECTED] wrote: Personally I don't like the C is Hashed::ByValues because it smacks of spooky action at a distance; I much prefer my notion of C %h{*@x} = 1. And in Perl 6 I have the horrible feeling that C %h = (*@x = 1) would expand to C %h = (1,2,3 = 1) ,

Re: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-25 Thread Luke Palmer
On 25 Jul 2002 [EMAIL PROTECTED] wrote: Luke Palmer [EMAIL PROTECTED] writes: On 25 Jul 2002 [EMAIL PROTECTED] wrote: Personally I don't like the C is Hashed::ByValues because it smacks of spooky action at a distance; I much prefer my notion of C %h{*@x} = 1. And in Perl 6 I

Re: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-25 Thread Aaron Sherman
On Thu, 2002-07-25 at 03:12, [EMAIL PROTECTED] wrote: Aaron Sherman [EMAIL PROTECTED] writes: my @x is Hashed::ByValues = (1,2,3); %h = (@x = 1); @x[1] += 4; Personally I don't like the C is Hashed::ByValues because it smacks of spooky action at a distance; I much prefer

RE: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-24 Thread Fisher Mark
As the last person to change the key hash algorithm, I'd like to chime in here with a request that each PMC provide a string that the key hashing algorithm can operate on. To some degree this is just selfish on my part -- I've got plans for upgrading the key hash algorithm in Perl 5 and Perl 6

RE: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-24 Thread Fisher Mark
But then sometimes you'd *want* hashing to be based on the content. OK, I'll bite -- when would you want this behavior? This behavior means that once you change the contents, the hash value would become irretrievable unless you restored the contents of the key. (Is this useful in functional

RE: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-24 Thread Aaron Sherman
On Wed, 2002-07-24 at 12:34, Fisher Mark wrote: But then sometimes you'd *want* hashing to be based on the content. OK, I'll bite -- when would you want this behavior? This behavior means that once you change the contents, the hash value would become irretrievable unless you restored

Re: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-23 Thread [EMAIL PROTECTED]
From: [EMAIL PROTECTED] If I have: $a = [ 1, 2, 3 ]; $b = [ 1, 2, 3 ]; %foo{$a} = 'A'; %foo{$b} = 'B'; Then I want C (%foo{$a} == 'A') %foo{$b} == 'B' to be true. Maybe this a case of And Now For Something Completely Similar. This looks like something we already have

Re: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-23 Thread Aaron Sherman
On Mon, 2002-07-22 at 04:36, [EMAIL PROTECTED] wrote: Now, I ask for PMC programmers to take care implementing this! Notice that, for example in arrays, arrays with the same length but different elements should return different hash codes (or try). But for the same elements MUST return

Re: RFC - Hashing PMC's albie@halfarrabio.di.uminho.pt

2002-07-23 Thread Dan Sugalski
At 9:36 AM +0100 7/22/02, [EMAIL PROTECTED] wrote: Um... not necessarily. Bordering on the 'not at all'. Perl 6 will apparently allow one to have things other than strings as keys to hashes. If I have: Yes. Hashes will take either strings or object IDs, depending on the hash. (The hash can