nope, they can't...trust me :) It's a very advanced extension library with significant nested structure...to represent it as a sequence of nested function calls would be too complex and difficult to read/maintain...if it could be done at all.
The example I gave was an extremely simple use case to get across what I want to do, rather than get bogged down in the particulars of each use case. I understand the use of functions, my extension library has a whole bunch of extension functions (I think it's up to about 30)...but also has about 40 extension elements for structures that are just too complex to be represented as extension functions. Some of these extension elements have return values that don't suit being turned into a node set. Is it that big an ask to be able to set a variable from an extension element? The patch submitted doesn't seem overly complex or have any impact on any other part of Xalan??? --- On Mon, 16/11/09, kesh...@us.ibm.com <kesh...@us.ibm.com> wrote: > From: kesh...@us.ibm.com <kesh...@us.ibm.com> > Subject: Re: Advanced Extension Element Question > To: xalan-dev@xml.apache.org > Received: Monday, 16 November, 2009, 3:43 PM > I'm > still not sure I understand why you > feel you have to express this as extension elements, when > extension functions > can already do what you (appear to) need? > > > > ______________________________________ > > "... Three things see no end: A loop with exit code > done wrong, > > A semaphore untested, And the change that comes along. > ..." > > -- "Threes" Rev 1.1 - Duane Elms / Leslie > Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html) __________________________________________________________________________________ Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7. Enter now: http://au.docs.yahoo.com/homepageset/ --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
