Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Readonly CPAN distribution.

Report information
The Basics
Id: 74902
Status: new
Priority: 0/
Queue: Readonly

People
Owner: Nobody in particular
Requestors: perlbug-followup [...] perl.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



CC: perl5-porters [...] perl.org, bug-Readonly [...] rt.cpan.org
Subject: [perl #109986] Readonly hash keys stay readonly after copying
Date: Sun, 12 Feb 2012 14:27:02 -0800
To: "OtherRecipients of perl Ticket #109986":;
From: "Father Chrysostomos via RT" <perlbug-followup [...] perl.org>
On Sat Feb 11 08:54:21 2012, jkeenan wrote: Show quoted text
> On Mon Feb 06 15:40:39 2012, dmcbride@naboo.to.org wrote:
> > > > This is a bug report for perl from dmcbride@cpan.org, > > generated with the help of perlbug 1.39 running under perl 5.10.1. > > > > > > ----------------------------------------------------------------- > > [Please describe your issue here] > > > > I'm using Readonly::XS, but I don't think this has anything to do > > with the problem other than exposing it.
> > I'm inclined to attribute the problem to Readonly::XS.
There are two problems. Readonly::is_sv_readonly is not a documented public interface, so anyone relying on is it doing something unreliable. Secondly, Readonly::XS itself is using undocumented Perl interfaces. SvREADONLY doesn’t necessarily indicate that a scalar is read-only. But it *does* indicate that a POK scalar has a read-only string buffer. -- Father Chrysostomos --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=109986


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.