The TODO should probably be deleted. I think the spec is now clear, but the
TODO is a reminder for me to check that the code actually implements the
spec as written. I suspect some corner cases such as
2005-08-25-12:00 = 2005-08-26+12:00
haven't actually been tested - although the XQTS test suite is actually
fairly thorough with such things.
> -----Original Message-----
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...] On Behalf Of
> Colin Paul Adams
> Sent: 30 August 2005 20:01
> To: saxon-help@...
> Subject: [saxon] Comparing date values
> In the source code for DateValue, there is a comment:
> "// TODO: the role of implicit timezone in date comparisons
> is unclear"
> but in F&O, April 2005, it says:
> "If either operand to a comparison function on date or time values
> does not have an (explicit) timezone then, for the purpose of the
> operation, an implicit timezone, provided by the dynamic context
> Section C.2 Dynamic Context ComponentsXP, is assumed to be present as
> part of the value. This creates a total order for all date and time
> This seems pretty clear to me. Is this a TODO you have overlooked, or
> is the WG re-considering this issue?
> Colin Adams
> Preston Lancashire
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development
> Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *
> Testing & QA
> Security * Process Improvement & Measurement *
> saxon-help mailing list