comment on

Yeah, LibXML. My tests *included* the time it took to extract the data from the tree.

Hm. So did mine. But I believe mine.

We use XML::Bare with a thin layer to compensate for it's awful interface (XML::Simple without ForceArray or any other option)

Hm. XML::Bare::forcearray( [noderef] )

S'funny init. It took less than a minute to disprove that. And after 5 minutes, I'm pretty sure I could use XML::Bare to read a file and get access to its content.

Conversely, when I tried to look up getDocumentElement, I completely crapped out after about an hour. You applied it to the return from load_xml() which is labelled $dom. So look in DOM. Nada. Maybe a Node. Nada. How about a parser, or a nodelist or a namespace? Nada, nada, nada!

Your idea of an "awful interface" is weird.

For me:

the best interface is the one I don't have to lookup more than once.
That means small.
The second best interface is one that makes it easy to lookup what I need to know.
That means the first page shows me enough to get something working.
Details, refinements and esoterica can be deferred to secondary pages if that cannot be avoided.
The third best interface is one that if it has to be large, is logically grouped.
That means, it starts by splitting the documentation along vertical lines. Ie. The way people need to use the interface. Eg, Read an XML; or write an XML; or edit an XML. etc. Not horizontally according to some arbitrary way the author decided to structure his code.
And it means starting with the basics in the root document, in the form of simple -- but complete -- worked examples of the main modes of use. And leaving the esoteric details for (preferably linked (and links that actually work)) secondary pages.
Not hitting the user in the face with a top level synopsis that contain every possible variation of the constructor and no indication of where to go from there.

XML::LibXML fails on every count.

Can we stop now, because we are once again doing nothing to help the OP; nor each other.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

In reply to Re^6: Is there any XML reader like this? (XML::Simple beats LibXML hands down in the speed stakes!) by BrowserUk
in thread Is there any XML reader like this? by ashok.g

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.