|
Re: XML::LibXSLT registered functions: a preliminary fix: msg#00032lang.perl.xml
Elizabeth Mattijsen wrote: This serves my purposes for the time being. But I wonder whether this is the right thing to do. On the one hand, you would only use this module if you're actually using registered functions. On the other hand, I feel this should be in integral part of XML:::LibXML and XML::LibXSLT. But that would mean an overhead to the destruction of XML::LibXML::Node objects that is not generally needed. This rocks! :) Personally I don't mind either way: I still like the idea of having registered functions work just the same for LibXSLT and XPathContext, and that requires loading a module anyway so loading yours too would be fine by me. I guess the question could also be: at the end of a document's life, do all individual nodes get DESTROYed or only those that are directly referenced from Perl? If all, then how high is the overhead for each? A DOM typically contains a lot of nodes, and even a small overhead for each could be a big one overall. Just my €2/100, thanks for doing this Liz! -- Robin Berjon _______________________________________________ Perl-XML mailing list Perl-XML@xxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | XML::LibXSLT registered functions: a preliminary fix, Elizabeth Mattijsen |
|---|---|
| Next by Date: | Re: XML::LibXSLT registered functions: a preliminary fix, Elizabeth Mattijsen |
| Previous by Thread: | XML::LibXSLT registered functions: a preliminary fix, Elizabeth Mattijsen |
| Next by Thread: | Re: XML::LibXSLT registered functions: a preliminary fix, Elizabeth Mattijsen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |