David Carlisle wrote:
That is of course if I've scaled up the input correctly, no comment
from the OP so far.
Yes I was going to mention last night that some of the code made some
assumptions that may or may not have been correct about the input.
In all cases for example the methods I suggested would be very
intollerent of any input that didn't have dark//ligght matching
exactly. It would be possible to code it up more defensively to trap
such cases and give warnings etc.
I am aware of these problems - reduced, minimal examples cannot
accurately describe real-life scenarios. But on the other hand, I find
complex examples hard to handle and learn from. This is why my main goal
(as mentioned in my earlier post) is to grasp the basic *idea*
(algorithm, concept) backing a specific solution implementation so that
I am hopefully able to transfer that knowledge to the actual (often much
more complex) problem at hand.
This is not to mean that giving actual XSLT code is bad! Most often, it
will nicely help demonstrate how that idea can be efficiently implemented.
-Christian
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--