Re: More XSL Discussion

[Sean Mc Grath]
> Okay! I'm half way there. An XSL processor is free to create the
> flow objects in any order it likes cos the place they are going in
> the resultant tree does not depend on creation order.  Fine. The
> part I still don't get is how the rule might be triggered 1000
> times?

It won't necessarily, but the point Paul is making is that you can't
make assumptions about the implementation.  Maybe the processor will
be multi-threaded, accessing the tree randomly and processing whatever
it comes across.  I don't know.  The point is that you can specify
transformations - from element tree to flow object tree - and you can
use programmatic functions to do that, but you can't fire off events
unrelated to the transformation and expect a sane result.  Using
writeln() triggers an event - the computer will, most likely, perform
some action upon encountering it, whose effects leave the scope of the
transformation.  That effect will be triggered every time the
transformation is called, and not necessarily linearly with the order
of the document's elements.

-Chris
-- 
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list