Michael Kay - 2005-08-06

Logged In: YES

The follow-up to this exposes another problem. Essentially
there is too much semantic processing being done when
enclosed expressions are parsed in scan-only mode.
Specifically, function calls are being fixed up to the
corresponding function declarations, which can lead to
spurious type errors later. The following patch fixes this:

In net.sf.saxon.expr.ExpressionParser before the line 1715
which reads

Expression[] arguments = new Expression[args.size()];


    if (scanOnly) {
        return StringValue.EMPTY_STRING;