This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I think the test here is intended to be declare variable $var := document {<a>123</a>}; $var[/*5] to match the comment. (:*******************************************************:) (: Test: Steps-leading-lone-slash-1 :) (: Written by: Jim Melton :) (: Date: 2009-10-01T14:00:00-07:00 :) (: Purpose: Verify xgc:leading-lone-slash implementation :) (: This expression is a syntax error: :) (: /*5 :) (:*******************************************************:) declare variable $var := document {<a>123</a>}; $var[(/)*5]
Also, in the catalog, the expected-error elements appear to be missing for: Steps-leading-lone-slash-1 Steps-leading-lone-slash-2 Steps-leading-lone-slash-3 Steps-leading-lone-slash-4 Steps-leading-lone-slash-5 Steps-leading-lone-slash-6 Steps-leading-lone-slash-7 Steps-leading-lone-slash-8 Steps-leading-lone-slash-9
Also, the catalog file contains a couple of probable errors. For test Steps-leading-lone-slash-14 the output-file is Steps-leading-lone-slash-15.txt. For test Steps-leading-lone-slash-15 the output-file is Steps-leading-lone-slash-16.txt.
Thanks very much for your report! I agree with each of your comments and have made the obvious corrections. I've marked the bug RESOLVED/FIXED and trust that you will mark it CLOSED as soon as you have verified the fixes.
Thanks, but I think you may have missed the output-file for Steps-leading-lone-slash-15 - it still references Steps-leading-lone-slash-16.txt. <test-case Creator="Jim Melton" is-XPath2="false" name="Steps-leading-lone-slash-15" FilePath="PathExpr/Steps/" scenario="standard"> <description>Verify xgc:leading-lone-slash implementation; valid expression.</description> <reflects-resolution>http://www.w3.org/Bugs/Public/show_bug.cgi?id=5727</reflects-resolution> <query name="Steps-leading-lone-slash-15" date="2009-10-01"/> <output-file role="principal" compare="Text">Steps-leading-lone-slash-16.txt</output-file> </test-case>
How embarrassing! Apparently, my fingers prefer typing a "6" instead of a "5" ;^) Anyway, once again, I claim that I've fixed it and marked the bug RESOLVE/?FIXED. Once again, I ask that you confirm it and, if you agree, mark the bug CLOSED. Thanks!
Thanks.