On Wednesday 07 June 2006 22:07, Perrin Harkins wrote:
> Me too. I don't think this is a bug, since it behaves normally for a
> Perl hash. It's been documented now, and I think that should be the end
> of it.
No, it does not. $r->pnotes->{key}=value behaves like a Perl hash.
$r->pnotes(key, valu
On Thu, 2006-06-08 at 09:21 +0200, Torsten Foertsch wrote:
> No, it does not. $r->pnotes->{key}=value behaves like a Perl hash.
> $r->pnotes(key, value) does not. But anyway if you all think it's okay the
> way
> it is I'll simply not use the second version anymore.
Oh, you're right, I remember
Perrin Harkins wrote:
> On Thu, 2006-06-08 at 09:21 +0200, Torsten Foertsch wrote:
>
>> No, it does not. $r->pnotes->{key}=value behaves like a Perl hash.
>> $r->pnotes(key, value) does not. But anyway if you all think it's okay the
>> way
>> it is I'll simply not use the second version anymor
were working around it. I wouldn't mind introducing $r->pnotes_noref or
sth to fix it, but that's
just me ;-)
Now that idea I LIKE!
+1
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant / http://p6m7g8.net/R
Hi,
>From my point of view changing pnotes in mp1/2:
--1 in mp1
--1 in mp2.0.x
+1 in mp2.x
for $r->pnotes_noref():
-1 mp1 who needs that?
-1 in mp-2.0.x adding this api would cause everybody to change code for
mp-2.x without any reason!
-1 in mp-2.x
Tom
Philippe M. Chiasson wrote:
> Perrin
