Inverted wxXmlNode sequence when adding nodes without using AddChild() from parent node

[Andrea Zanellato]

I noticed that, when adding wxXmlNodes inside a wxXmlDocument,
specifying the parent in their constructor, not using
parentNode->AddChild( childNode ), they seems to be added with an
inverted order, including subnodes.
I didn't tested this if it happens only using recursions or in all cases
but:
is this normal and AddChild is mandatory for some reason, should this be
documented or kind of bug?

Regards

Andrea