RE: Template recursion, StackOverflowError, saxon:while a nd variable assignability

Hi

> For assign, I have a few use cases but they are quite intricate.
> 
> I could try to extract their essence and return with more 
> info but is this 
> forum the right place for this?

Yes, because saxon:assign is what needs replacing.
Yes, because saxon:something-better is the most likely thing to
appear soon.
No, but where else can XSLT 2.1/3.0 be profitably discussed?
 
> Just from memory I would say that typically they are global 
> accumulators 
> that maintain some form of changing status maintained and shared by 
> multiple processes, and changing over time, in real-time, for 
> example, 
> real-time streaming security analysis, in parallel processing 
> pipelines, 
> over graphs of potentially billions of nodes (that you would 
> not want to 
> copy over too often, especially on-line), 24/7, with a large 
> number of 
> users (ex: 120 000 000/week).

Quite some time ago, possibly in Proc ACM, I came across a paper
showing that a functional language was finally outperforming
Fortran on big array computations.

A functional language appears to do lots of copies, but by ensuring
that the compiler understands their lifetime, the compiler can
actually do re-use.

So 'copying' mega-graphs in order to do an 'assign' isn't necessarily
a problem, just so long as the compiler eliminates the copy and
ends up doing your saxon:assign declaratively.

Perhaps this is an optimisation that can be performed as-is.
Perhaps there are a few programming practices that could be
observed to ensure that techniques such as tail-recursion can
be more generally effective.

Michael?

        Regards

                Ed Willink


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click