[
http://issues.apache.org/jira/browse/XERCESC-1409?page=comments#action_63347 ]
David Bertoni commented on XERCESC-1409:
----------------------------------------
I haven't done any measurements, but since we're getting rid of a library call,
plus some pointer arithmetic, I'm sure this will be a win. In my usage, I'll
be calling into this code very often, so every little bit counts.
As far as the transcoding is concerned, I agree with you. Perhaps the thing to
do is to rely on a stack-based buffer for strings up to a certain length, plus
couple that with a dumb transcoder that only does ASCII characters. That would
remove both an allocation and deallocation in most cases, plus the transcode
call.
What do you think?
> More efficient error detection for XSValue, XMLDouble, and XMLFloat
> -------------------------------------------------------------------
>
> Key: XERCESC-1409
> URL: http://issues.apache.org/jira/browse/XERCESC-1409
> Project: Xerces-C++
> Type: Improvement
> Components: Validating Parser (Schema) (Xerces 1.5 or up only)
> Versions: 2.6.0
> Reporter: David Bertoni
> Assignee: David Bertoni
> Attachments: patch.txt
>
> These classes check for invalid characters in numeric values by determining
> if a C run-library routine reached the end of the string. There is a more
> efficient way to do this than what the current code does.
> I am attaching a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
