Michael Kay wrote:
>> There are other factors - null termination of returned
>> strings and attribute value normalization can both cause
>> string copies. These can both be disabled, although disabling
>> the latter would mean Faxpp would be non-conformant.
>
> But it should presumably be possible to design the API so that attribute
> value normalization is only done for attributes that the user wants to
> process.
Faxpp doesn't abstract the attribute values to the extent needed to do
that automatically - although it would be interesting to expose the
attribute value normalization function, so that users could run it on
un-normalized attribute values themselves. Thanks for the suggestion.
John
--
John Snelson, Oracle Corporation http://snelson.org.uk/john
Berkeley DB XML: http://www.oracle.com/database/berkeley-db/xml
XQilla: http://xqilla.sourceforge.net