Re^2: Maintaining parent child order when printing summarized XML Twig

I'm afraid a sample that would demonstrate what I'm talking about would be too big to post here. I've narrowed it down now and believe that what's happening relates to having to flush a twig after the document is parsed in order to obtain the last element. For some reason the last Item is just one huge concatenated block of text. How big can your code get before it's just too big to post?

Comment on Re^2: Maintaining parent child order when printing summarized XML Twig

Replies are listed 'Best First'.
Re^3: Maintaining parent child order when printing summarized XML Twig by GrandFather (Saint) on Nov 19, 2007 at 22:43 UTC
Too big is "more than required to demonstrate the issue". It is very unlikely that you need a large amount of data or code to demonstrate the issue, but you may need to do a fair amount of work to focus the code and data down to a sensible minimum. In the process you are also quite likely to find the issue yourself - but that need not be a problem. ;) Perl is environmentally friendly - it saves trees	[reply]

Replies are listed 'Best First'.

Re^3: Maintaining parent child order when printing summarized XML Twig
by GrandFather (Saint) on Nov 19, 2007 at 22:43 UTC

Too big is "more than required to demonstrate the issue". It is very unlikely that you need a large amount of data or code to demonstrate the issue, but you may need to do a fair amount of work to focus the code and data down to a sensible minimum. In the process you are also quite likely to find the issue yourself - but that need not be a problem. ;)

Perl is environmentally friendly - it saves trees

[reply]