Re: [xslt] [PATCH] xslt extensions as modules, take 2
- From: Joel Reed <joelwreed comcast net>
- To: thevakoc-xml yahoo com, The Gnome XSLT library mailing-list <xslt gnome org>
- Cc:
- Subject: Re: [xslt] [PATCH] xslt extensions as modules, take 2
- Date: Wed, 5 Jan 2005 22:36:49 -0500
On Wed, Jan 05, 2005 at 09:16:42PM -0500, Joel Reed wrote:
> On Tue, Jan 04, 2005 at 10:39:46AM -0800, Mark Vakoc wrote:
> > --- Joel Reed <joelwreed comcast net> wrote:
> > I guess what I'm saying is that a extension module shouldn't be that dynamic :)
> > That is avoid the logic to load it on demand and instead require that the
> > caller "register" the plugin module within their application rather than have
> > libx* try to find it on it's own. Think of adding custom i/o handlers to
> > libxml2. How can that be dynamically discovered?
thinking about this more it seems applications can already register extensions
and functions with xsltRegisterExtModule* - so i'm still struggling to see
how this adds additional value over just using those funcs.
jr
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]