[ 
https://issues.apache.org/jira/browse/XERCESC-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boris Kolpackov closed XERCESC-1503.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.1

I think most of these were implemented in 3.0.1. If not, please reopen with an 
updated patch.

> Suggestions for small improvements in src/xercesc/util/ [patch]  and samples/
> -----------------------------------------------------------------------------
>
>                 Key: XERCESC-1503
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1503
>             Project: Xerces-C++
>          Issue Type: Improvement
>    Affects Versions: Nightly build (please specify the date)
>            Reporter: Jeroen N. Witmond
>            Assignee: cargilld
>             Fix For: 3.0.1
>
>         Attachments: xerces-c-vanilla.patch
>
>
> The attached patch against svn revision 289713 makes the following small 
> usability improvements:
> - make a number of static helper methods in XMLUri.hpp public. They are 
> useful when for instance normalizing a URI. 
> - adds methods to XMLString.hpp and XMLString.cpp to release strings using a 
> memory manager. In XMLString.hpp the comments/documentation are updated as 
> well.
> The patch also fixes the compilation warning about comparison between signed 
> and unsigned in
> src/xercesc/validators/schema/SchemaElementDecl.hpp. This problem was 
> mentioned before on the c-dev list, but the fix has not made it to svn yet.
> For an improvement in samples/ I second the suggestion made by Neil Graham on 
> 10 december, 2003: "I'd also like to deprecate the SEnumVal and EnumVal 
> samples eventually; we certainly shouldn't be going out of our way to show
> people how to use Xerces's internal interfaces!".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to