comment on

Do you want the output file to have the same order of XML tags as the input file?

I built an automated test equipment (ATE) configuration and test system using XML::Simple, but I didn't like it because it changed the order of the XML tags between the input and the output. I switched from XML::Simple to XML::Twig and solved this problem.

After doing this, I thought that maybe XML is not so great for this type of application. I wanted human-readable files that were also easy to parse with a computer. I also wanted to add tags in the future without breaking old files. XML seemed like the right choice but it was not so easy to achieve these goals. Recently I have tried YAML with the same goals, but this has not been so great, either. I am still looking for a better solution.

Now I think I should use something like YAML, but I should write my own parser.

It should work perfectly the first time! - toma

In reply to Re^3: XML parser by toma
in thread XML parser by hakana

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks