Sorry for the late answer, I was sick.
The easy fix is that you need to cut $this_tweak before you can safely call replace. I will add a cut if the element is still part of a twig in the next version, thanks.
A couple more things: if you use warnings you will see that @matches[0] is "best written as" $matches[0] (note the $). Also the handler (the pruner sub) receives 2 parameters, the twig and the element, so you could write my( $twig, $this_tweak)= @_ (you might already know that, but I'd rather newcomers read it here ;--). And finally, using get_xpath to get the previous tweak seems a bit wasteful. You could use simply $this_tweak->previous_sibling( qq{tweak[\@name="$tweak_name"]}), or even keep an index of tweak_name => tweak_element, for direct access.
Does that help?
In reply to Re: XML::Twig replace method behaving counter-intuitively
by mirod
in thread XML::Twig replace method behaving counter-intuitively
by Human
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |