Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Computational complexity of accessing the Nth item in a sequence and in a node-set

From: Dimtre Novatchev <dnovatchev@--------->
To:
Date: 1/3/2005 9:36:00 PM
On Mon, 3 Jan 2005 21:06:40 -0000, Michael Kay <mike@xxxxxxxxxxxx> wrote:
> > So, if I have understood correctly, having
> >
> >    $sequence[last()]
> >
> > (and somehow more than one reference to $sequence)
> > will guarantee that any further access to the items of $sequence will
> > be performed in constant time?
> 
> No guarantees: but yes, that's what I would expect to happen.
> >
> > Cant this be pre-computed automatically by the XSLT processor?
> > Something like computing a function with @memo-function="yes", but
> > done by the XSLT processor?
> 
> I'm not clear what you mean.


I want a "fast-sequence" that behaves like an array. In the
constructor implementation I'd put a reference to
          $sequence[last]

probably not a direct reference, but by calling a function myLast()
that returns
       $sequence[last]

I want this to be calculated only once. My question was will it be
successful to use the

saxon:memo-function="yes" attribute 

on the definition of myLast()


Cheers,
Dimitre.


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent