Skip Menu |

This queue is for tickets about the XML-Simple CPAN distribution.

Report information
The Basics
Id: 94669
Status: resolved
Priority: 0/
Queue: XML-Simple

People
Owner: grantm [...] cpan.org
Requestors: p.krupp [...] web.de
Cc:
AdminCc:

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



Subject: arry or hash
Date: Sat, 12 Apr 2014 14:59:09 +0200
To: bug-XML-Simple [...] rt.cpan.org
From: p.krupp [...] web.de
Hi,
 
maybe i just misunderstand something, but i think the script xml_simple_tst.pl misbehaves. If you read in hash.xml $ref->{script} is a HASH-Ref, if you read in array.xml it is an ARRAY-Ref. The only difference between hash.xml and array.xml is, that in hash.xml the name of an atribute in the /scripts/script element is 'key', whereas on the same position and with the same value there is an attribute called 'mkey' in array.xml.
 
If it is not a bug, could you please explain this?
 
Best regards
Paul
 
 
Download xml_simple_tst.tar
application/x-tar 10k

Message body not shown because it is not plain text.

The default value of the KeyAttr option is what's causing the difference you're seeing: https://metacpan.org/pod/XML::Simple#OPTIONS If you're writing new code, it's probably better to start with a different module. I almost always use XML::LibXML as described here: http://www.perlmonks.org/index.pl?node_id=490846 But if you decide to stick with XML::Simple, please read this: http://www.perlmonks.org/index.pl?node_id=218480 Regards Grant
Subject: THANKS Aw: [rt.cpan.org #94669] Resolved: arry or hash
Date: Mon, 14 Apr 2014 14:13:38 +0200
To: bug-XML-Simple [...] rt.cpan.org
From: p.krupp [...] web.de
Hi Grant,
 
thank you for your answer. I will follow your links.
 
Best regards
Paul
 
Gesendet: Sonntag, 13. April 2014 um 00:02 Uhr Von: "Grant McLean via RT" <bug-XML-Simple@rt.cpan.org> An: p.krupp@web.de Betreff: [rt.cpan.org #94669] Resolved: arry or hash
<URL: https://rt.cpan.org/Ticket/Display.html?id=94669 > According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message.