pugixml 1.2 release
pugixml-1.2 is finally out. This is a major release with lots of new features and compatibility improvements (read the changelog for details).
Highlights for this release include:
- New optional header-only compilation mode that does not require compiling pugixml sources and can improve performance for certain applications due to inlining;
- Enhanced interface for PCDATA manipulation using an xml_text object;
- C++11 range-based for-loop support for node/attribute iteration;
- Compatibility improvements for many mobile platforms (including Android, Windows Mobile and other SDKs/devices).
You can download the source package or get the new version from Subversion using the latest tag (http://pugixml.googlecode.com/svn/tags/latest).
pugixml 1.0 release
pugixml-1.0 is out. This is a major release with lots of fixes/improvements (read the changelog for the details). The most important changes are:
- XPath implementation was considerably improved – variable support was added, exceptions and STL are no longer required for XPath to function, query evaluation performance was improved and several bugs were fixed.
- All deprecated functions and types were removed
- File loading/saving functions can now work with wide character paths
You can download the source package or get the new version from Subversion using the latest tag (http://pugixml.googlecode.com/svn/tags/latest).
New project site
pugixml now has a new home, pugixml.org. This site acts as a frontend for all pugixml-related stuff (downloads, documentation, support and other information). Additionally, there is a news feed, which you can subscribe to via RSS.
All downloads, documentation, Subversion repository and issue tracker are still hosted at Google Code; the existing links still work, and this is not going to change.
pugixml 0.9 release
pugixml-0.9 is out. This is a major release with lots of fixes/improvements (read the changelog for the details). The most important changes are:
- Unicode support is completely reworked: now pugixml can be configured to use wchar_t instead of char for all string-based interfaces; also encoding conversion is performed during parsing/saving (with automatic encoding detection). All popular Unicode encodings are supported.
- New version features a new documentation, with detailed description of library interface and behavior, more samples, quick-start guide and so on.
- There are new functions for loading document from memory; they do not require the input buffer to be null-terminated. Old functions still work, but are deprecated and will be removed in the future version.
Also there are a lot of other changes, including performance and memory consumption improvements.
