XML::Simple Output

[batkins]

I'm using XML::Simple to read in an XML file, make a change to it, and then output the resulting XML. However, the output isn't formatted quite the way I want it. This is my code:

use XML::Simple;

$xml = XMLin("pre.xml");
$xml->{core}->{test} = 'testeroo';
$res = XMLout($xml);

print $res;

This is pre.xml:

<config>
<core>
    <variable>ere</variable>
</core>
</config>

And this is the output:

<opt>
  <core test="testeroo" variable="ere" />
</opt>

Is there any way to make the result look like:

<opt>
  <core>
    <test>testeroo</test>
    <variable>ere</variable>
  </core>
</opt>

If not, is there some other module that can make this happen?

[Chmrr]

Check out the noattr option to XMLout:

% perl -w
use XML::Simple;

$xml = XMLin("pre.xml");
$xml->{core}->{test} = 'testeroo';
print XMLout($xml, noattr => 1);
^D
<opt>
  <core>
    <test>testeroo</test>
    <variable>ere</variable>
  </core>
</opt>
<

Update: You may also be interested in the rootname => 'config' option.

[Cody Pendant]

I'd say this is rapidly becoming a Frequently Asked Question, and I say this in all humility because I've asked it myself. I've definitely seen it a couple of times lately.

Is there a place for this in Q & A?

Why does this module require two attributes to be set in order to make output have the same structure as input? I'm not complaining, I genuinely want to know. It's not terribly simple in that respect at least.

[grantm]

Why does this module require two attributes to be set in order to make output have the same structure as input?

XML::Simple is optimised for reading XML. Some of the things it does to make your life easier when it reads XML make things more difficult if you try and write XML back out again. But if you're anything like me then you read XML far more often than you write it. The two operations have very little in common so one tool is unlikely to be well suited to both.

I'd be the first to admit that the XML::Simple API is a mess. The primary reason is that it wasn't planned as a general purpose XML manipulation tool. It was designed for reading XML config files. The code to write XML back out again was added on later. If I had set out to write a tool that could round-trip XML perfectly every time then I would have ended up designing some sort of DOM-type thing and at some point I would have seen the error of my ways and given up.

I'd say this is rapidly becoming a Frequently Asked Question

Perhaps, but I'd wager that most people who are asking have not read the XML::Simple documentation sitting on their own hard drive, or the XML::Simple FAQ sitting next to it. The original poster for example had a choice of 22 options and apparently didn't even try one! The ForceArray option which would be one solution to the original question is even singled out in the documentation as one of the two most important options you need to read about before you use the module. You can lead a horse to water ...

[Cody Pendant]

Hi, thanks for that. I think part of the problem is that baffled, frustrated people who are just getting started with XML see something called XML::Simple and think it's the answer to all their prayers. I know I did.

Maybe I could suggest putting this one particular issue in the POD?

And you know what? I just clicked on the link to the XML::Simple::FAQ on search.cpan.org and it's a 404...

[PodMaster]

Is there a place for this in Q & A?

XML::Simple already has a FAQ (in addition to complete documentation), so I'm not so sure (the Q&A section is not exactly a module specific FAQ).

Why does this module require two attributes to be set in order to make output have the same structure as input? I'm not complaining, I genuinely want to know. It's not terribly simple in that respect at least.

That's how the module works (ask the author).