No, it doesn't. First, it worked fine with any change whatsoever. Second, it works with without NoAttr too. It even produces the same tree in both cases.
use strict;
use warnings;
use Data::Dumper;
use XML::Simple;
# The fastest existing backend for XML::Simple.
local $XML::Simple::PREFERRED_PARSER = 'XML::Parser';
my $xs = XML::Simple->new(
NoAttr => $ARGV[0],
KeepRoot => 1,
NormaliseSpace => 1,
);
my $tree = $xs->parse_string( <<'__EOI__' );
<BILLING>
<ACCOUNT></ACCOUNT>
<RTN></RTN>
</BILLING>
__EOI__
print( Dumper( $tree ) );
print( $xs->XMLout( $tree ) );
$ perl a.pl 1
$VAR1 = {
'BILLING' => {
'RTN' => {},
'ACCOUNT' => {}
}
};
<BILLING>
<ACCOUNT></ACCOUNT>
<RTN></RTN>
</BILLING>
$ perl a.pl 0
$VAR1 = {
'BILLING' => {
'RTN' => {},
'ACCOUNT' => {}
}
};
<BILLING>
<ACCOUNT></ACCOUNT>
<RTN></RTN>
</BILLING>
Update: I originally said it produced a different structures.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.