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?

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).

We tried other methods but had to resort to assign in some cases. Finding 
an alternative could involve some language redesign or changes that may not 
be as simple as supporting assign.

Maybe these problems are not for XSLT but that would be quite unfortunate 
because it is a fascinating language for heavy graph processing in an 
on-line environment.

In any case, we would be happy if a more elegant, yet efficient alternative 
can be introduced, but quickly before applications are widely sold and 
installed !

How should we do this ?

Thank you
Andre



At 05:51 2005-06-15, you wrote:
> Hi Michael, Andre
>
> > I understand your issues but there are a few cases that
> > cannot be resolved without saxon:assign and just as much as
> > we try to avoid it with everything we can, sometimes there
> > are just no reasonable alternatives. ...
> ...
> > In fact, there is still a very limited set of indispensable
> > saxon extensions that should be added to the standard and the
> > 2 main ones are eval/evaluate and assign/assignable.
>
> eval seems a very plausible addition to the lanaguage.
>
> assign absolutely is not. Perhaps it's worth trying to classify
> the problems that assign is solving so that a reasonable alternative
> can be formulated.
>
> The one problem I have been tempted to use assign for was to
> cache a friendly unique identifier into a newly created node. This
> could be resolved by introducing some form of constructor.
>
>         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
> _______________________________________________
> saxon-help mailing list
> saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/saxon-help



-------------------------------------------------------
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