Sorry about that. I meant to update that information. I'll
go through it, retest and update as soon as possible.
Tom
Gunnlaugur Thor Briem wrote:
> Hi,
>
> I've been trying to ascertain the current status of XSLTC
> compliance by reading xml-xalan/java/xsltc_todo.xml but I
> find that it is last-modified on June 20 ... at XSLTC's
> recent rate of development, this leads me to believe that
> it is woefully out of date for a document of its kind! :)
>
> So in the interests of both accessibility for prospective
> new contributors and easier feasibility assessment for
> integrators, could someone in-the-know please clean out
> the most significant cobwebs from xsltc_todo.xml ?
>
> Failing that, what I'm most eager for is the current status
> of fundamental noncompliance issues such as these (from
> "Known Problems" in xml-xalan/java/xdocs/readme.html):
>
> - Casting variables: XSLTC requires you to explicitly type cast values
> returned by variables or expressions, when you use them in tests.
>
> - Order dependency of conditions within a predicate
>
> - [1] should be treated equivalent to position()=1, but it is not
>
> - XSLTC fails to match existing nodes when match expressions have
> multiple steps with predicates containing the position function.
>
> Are all of these still in effect? Are any of them
> work-in-progress, or are they all sitting intact,
> waiting for the mythical "developer-with-free-time
> on-his/her-hands" to put them through the wringer?
>
> Thanks!
>
> - Gulli
>
> ---
> Gunnlaugur Thor Briem at Dimon Software
>
> "A person without a sense of humor is like
> a wagon without springs -- jolted by every
> pebble in the road." - Henry Ward Beecher
