This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Functional programming in XSLT


> That's one vote for exsl:result (Uche) and one vote for exsl:return
> (you).  Any other opinions?

I think the best choice depends on whether the processing of exsl:function
is expected to terminate as soon as exsl:result is instantiated (in which
case it would be better to name it exsl:return).

You seem to be in two minds as to whether multiple exsl:result elements
should be allowed, perhaps to build up a compound result. If you go the way
you appear to be leaning, and only allow a single instantiation then
immediate termination would also solve all the issues about what to do when
multiple result elements are instantiated - it just won't happen!

FWIW, a single instantiation of exsl:return which terminates exsl:function
immediately would get my vote.

Dave Hartnoll.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]