[for the record] <anonymous> wrote: > looks good. My initial comments are this: > > I'd like to see a XPathEvaluator interface expose only one method > instead of the evaluatAs* methods. It should be called compileXPath and > should return an XPath object. so that you can turn an XPath statement > into an XPath pre-evaluated, and reusable object. That XPath object > should expose the evaluation methods (minus the XPath string of course) > and an additional method for determining the result type of the > expression. > > I'd like to see this XPath object expose a method that tells you what > kind of result will be returned (Nodeset, Boolean, String, Number...), > so that when generic query engine is evaluating the expression, it knows > which method to actually call. In the current interfaces, it seems as > though the programmer has to be a mind reader ahead of time in order to > determine which evaluation method to call.Received on Thursday, 21 June 2001 12:18:11 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:24:53 GMT