(Update: but I will want to avoid any walking around the stack - "where I am" is easy in the particular case because I have an instance variable for it. As a rule it is best to stick to pushing and popping.)
re XML::Twig, there were other requirments that needed to be met by various projects for my client, not just the size of the XML files and these were not met by XML::Parser or Expat. It was obvious fairly early on that I needed to be able to code features into the main part of the parser so I had to have control over it and new requirments since then have also deviated from what is currently availabkle in the XML namespace, such as tolerating extra characters between tags that do not conform to "standard" XML whatever that might be.
XML::Twig suffers from my point of view in that respect from being built on XML::Parser.
At some point I will have to make a list of the special features and think up a new name for the module. XML::Deviant perhaps ;)
-M
Free your mind
In reply to Re^2: Nesting below emptiness and/or inverting a hash.
by Moron
in thread Nesting below emptiness and/or inverting a hash.
by Moron
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |