Hello John,
If I understand correctly, that might suit my purpose. Does it just AUTOLOAD its methods, and then dispatch the method calls that you don't implement in your subclasses to the contained object?
What I have done in the mean time is to store the subclass name in the XML::LibXML::Element objects as an attribute, and then use that to bless the references returned by my lookup routine (which is just a wrapper around findnodes() that does the bless()ings). Unfortunately this is a little bit inefficient when findnodes() returns a large nodelist, but it works, and it seems to perform reasonably well for my application. I think that your solution is cleaner, and will most likely perform better. I'll take a look at it.
Thanks,
-brian
In reply to Re: Re: Re: Re: Is it a bad idea to subclass XML::LibXML ?
by nenbrian
in thread Is it a bad idea to subclass XML::LibXML ?
by nenbrian
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |