It would have been much better to (more or less) formally define the
concept of "tail recursion" and make it clear that a good implementation
can (or should) optimize tail recursion with iteration.
I completely understand your position. But I think one of XSLT’s really
surprising strengths is the number of people who would not self identify
as “programmers” who are able to build significant systems with it.
I’m pleased that xsl:iterate makes a certain class of problems easier to
solve even for folks who might be intimidated by the notion of writing
recursive functions and unfamiliar with the jargon of folds and tail
recursion.
I’ve personally unwound at least a couple of tail-recursive functions
and turned them into xsl:iterate precisely because I think it’ll be
easier for a future customizer of the stylesheets to understand what is
going on.
Be seeing you,
norm
--
Norman Tovey-Walsh <ndw(_at_)nwalsh(_dot_)com>
https://nwalsh.com/
There are 350 varieties of shark, not counting loan and pool.--L. M.
Boyd
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--
signature.asc
Description: PGP signature