or for something only a little different it may be worth taking a look at XML::Twig.
The code you present could be mapped easily into almost any XML parsing module. What are the new areas that you want to be able to handle that DOM is a pain for?
I notice that at one point you have a for loop over 'SA_PATIENT' elements and retain data from the last element found which is later saved to @patdemo. Is it intended behaviour that you only retain the last element's data?
By the way you could have trimed the code down to about a dozen lines and included some sample data (keep the data small too) for posting purposes - then people may feel more inclined to post sample solutions using other XML systems (I started, but couldn't be bothered - too much code all the same).
In reply to Re: Rewriting XML::DOM based module as XML::SAX
by GrandFather
in thread Rewriting XML::DOM based module as XML::SAX
by Cappadonna3030
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |