Custom memory allocation for pugixpath (STL)

[GoogleCodeExporter]

What feature do you require in pugixml?
Currently, the custom memory management is applied only to pugixml. Will it be 
possible to extend this to pugixpath as well? i.e. can we make the STL related 
code to use the provided memory management functions.
What do you need this feature for?
To ensure that all parts of our application uses the provided memory management 
functions.
If you already have a patch, please attach it to the issue.
No.

Original issue reported on code.google.com by sures...@gmail.com on 10 Sep 2010 at 9:21

[GoogleCodeExporter]

In fact, this is already implemented in trunk. XPath does not use STL 
internally (and all XPath allocations go through custom allocators); the only 
place which uses STL is xpath_query::evaluate_string (there is a different 
overload available that does not use it).

You can either use the trunk version, or wait for the next release (which is 
expected in two months or so).

Original comment by arseny.k...@gmail.com on 10 Sep 2010 at 11:44

• Changed state: Accepted

[GoogleCodeExporter]

Thanks. I will take a look in the trunk.

Original comment by sures...@gmail.com on 13 Sep 2010 at 3:19

[GoogleCodeExporter]

pugixml-1.0 is out; all internal allocations now use the custom allocation 
functions, if any.

Original comment by arseny.k...@gmail.com on 31 Oct 2010 at 6:21

• Changed state: Fixed