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: Jumping out a loop AND Starting loop at another node



Tanz Mohammad first asked:
>I am trying to start the loop at node 4...
and later asked:
>I want to jump out the loop at...

I think it's important to jump out of such thinking right now!
Picture it this way: if the select of your for-each selected 16 nodes,
and your XSLT processor were running on a computer with 16 processors,
all 16 nodes could actually get processed at the same time (if the
XSLT processor were written to do so). When you look at it that way,
you can see why one thread ("iteration" in the fallacious view) can't
set a value for another thread to read, and why you can't skip over
the first 3 or the 2 after value="x" -- there is NO "first" or "after"
in the processing. Document order or xsl:sort controls the order in
which outputs must be placed on the output tree, but it doesn't
affect how the processor sequences or parallelizes internally.

If you want a for-each to apply to a limited set of nodes, you must
select only that set.
.................David Marston


 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]