A touch of API sloppyness in Xalan C 1.3

[Brian Quinlan <br...@sweetapp.com>]

In Xalan C 1.3, there is a new pure virtual function in the "Function"
class:

virtual const XalanDOMString
getError() const = 0;

I don't think that extensions should be required to implement this
function, since it may not be relevant to them if they reimplement:

execute(
	XPathExecutionContext&			executionContext,
	XalanNode*					context,
	const XObjectArgVectorType&		args,
	const Locator*				locator) const;

I think that the above function should be the only "execute" function
part of "Function", which should only have pure virtual functions. An
implementation helper could be placed in a subclass.

IMHO, of course :-)

Cheers,
Brian
(who had to write a useless getError)