Paths aren't only expressed as a set of indices-- that's pretty useless when it comes to XML, in fact. The power of XML is the semantic involved in tags abstracting the structure as a set of indexed data (/html/head/title is more robust, meaningful and accurate than "1 1 2"). The important part of the API would be making a node's children enumerable, not simply getting at a specific node. If we're only talking about accessing a specific node (the 2nd element of the 1st child of the root), XPath works much better. However XPath is limited because it doesn't solve the enumeration problem. Yes, XPath can return collections (//li, for instance), but how to "return a collection" in mIRC brings us back to the same problem I discussed above.
Using your $xmlread how would i take node $xmlread(1 1 2) and then loop over its children? That's the question the API would need to answer.
