Lionel Villard wrote:

XPath API implementation:

- Semantic analysis: currently no semantic analysis is performed.
Therefore the _expression_ a/(43+23)/f is correctly parsed but an error
should be raised.
 IMO, I think it would be OK to let the application that uses the XPath API find/report these errors. In the case above, if the app supports static typing, then it can report an error given that not(xs:integer <: node).
Parser:

- function call: right now, 'function call' AST nodes are created without
knowing the name of the function, which prevent fine-grain specialisation
at construction time. The same problem occurs with sequence types. I just
need to figure out how to do it in javacc.
 Could you elaborate this a bit more?

 Thanks.

-- Santiago

Reply via email to