logo       

Re: XML::LibXSLT registered functions: a preliminary fix: msg#00038

lang.perl.xml

Subject: Re: XML::LibXSLT registered functions: a preliminary fix

Elizabeth Mattijsen wrote:
At 15:45 +0100 12/11/03, Robin Berjon wrote:
Elizabeth Mattijsen wrote:
Well, I posted a message about this about 10 days ago or so: from what I understood there is that LibXSLT and XPathContext are two different modules, with two different approaches and never the twain shall meet.

I must have been sleeping or something.

The message was posted on Nov 30, and titled "LibXSLT / XPathContext interaction". You actually replied to it, so I guess you must have been asleep while typing... ;-)

Honestly, I wouldn't be in the least surprised ;)

Well, maybe we should try to get that together, although I must admit I don't think I'll be a user of XML::XPathExt. But what I _do_ need is reliable registered Perl functions in XML::LibXSLT. Ones that don't blow up and are reliable without (too much) leaking when used in mod_perl.

Yes, I understand what you need but the point is that with XML::XPathExt the extensions you create (and that you may use only for XML::LibXSLT) and release to CPAN can be used also by happy XPathContext users (and likely in the future yet others, such as XML::XPath users, users of Michel's XPath extensions to XML::Twig and XML::DOM, XML::DOM3::XPath users, etc...). It's just a simple way of avoiding code duplication.

I'm happy having to dance around a bleeding chicken if it means I get extension functions that work well ;)

Hmmm... images of BTVS appearing before my flu stricken eyes ;-)

Perhaps I should take a break away from london.pm ;)

Ok, if I would create patches, where would I need to send them? Here?

Depends to what ;) But sending them here makes sure that the maintainers get them, and that users in a hurry to use them before the next release can benefit from them as well.

I need to get a good working registered function implementation by the end of the year. It may leak (if it has to), but it may not segfault. Ever. That's my personal goal.

I'm also happy with something that leaks (reasonably ;) so long as it doesn't segv. It seems logical to get something to work before ironing out the bugs ;)

--
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>
Google Custom Search

News | FAQ | advertise