Front page | perl.perl5.porters |
Postings from April 2008
On Fri, Apr 25, 2008 at 02:58:37PM +0100, Nicholas Clark <nick@ccl4.org> wrote:
> I'm not quite sure why you consider a module that was released *after* 5.10.0
> that has a test failure to be a bug in 5.10.0, given that the version
> of the module at the time of the release passed.
Because the module works fine with 5.10.0, so it is a regression?
> The assertion failure is due to a change in decode_json, from
Both versions use SvCUR, so this change doesn't cause it, the problem was
either there all the time or not there at all.
So earlier versions of the module would have run into the same problem
with post-5.10.0 code.
> You mention "other XS modules". Which other XS modules?
I saw that, too, but can't remember which ones it was. Since it doesn't
happen with any release version of perl I didn't think much about it.
Also, if SvCUR no longer works safely on scalars and I have to resort to
undocumented behaviour (Checks the private setting. Use "SvPOK".) then I
would expect this issue to be much more common.
I am happy to check any private flags, of course, but since this was never
documented, I am pretty sure many moduels will fail.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / pcg@goof.com
-=====/_/_//_/\_,_/ /_/\_\
Thread Previous
|
Thread Next