Pygccxml

-------------

1. Fix problem with argument without names when building declaration string (55)

-------------

1. Improve error message when no castxml or gccxml is found.

2. Fix compilation of tests with c++11.

3. Fix patching of enums in default arguments for C++03.

4. Version numbers are still tagged with the v prefix (1.7.4 was correctly tagged),
as this is recommended by GitHub. The version number in the __init__.py and
setup.py files are without v prefix, because this is what pip requires.

Thanks to the following people for their contribution to this release:
Ashish Sadanandan

-------------

1. CV-qualified arrays were not being handled correctly by type traits
manipulations functions. For instance, 'int const[N]' would not be
detected as 'const'. Similar problems existed for volatile qualified
arrays too. See 35 for more details. A newer version of CastXML is
recommended (xml output version >= 1.138)

2. Close subprocess stdout stream once value has been read.
Fixes some warnings under python3.

3. Since this release, pyggcxml's version numbers do not contain the ``v``
prefix anymore. This was breaking distribution on PyPI (pypi.python.org).

4. The documentation is now at http://pygccxml.readthedocs.io/

Thanks to the following people for their contribution to this release:
Ashish Sadanandan

-------------

1. Addition of an is_union() method in the type_traits module.

2. type_traits.smart_pointer_traits will now classify std::shared_ptr as a
smart pointer (only boost::shared_ptr was recognized before)

3. Fix a regression in undname_creator_t.format_argtypes

4. C++xx flags are now correctly passed to CastXML. Allowed flags are:
"-std=c++98", "-std=c++03", "-std=c++11", "-std=c++14", "-std=c++1z"
Thanks to Mark Moll for the fix.

5. Add better support for "typedef (class|struct) {} foo;" syntax when using
CastXML. GCCXML did not recognize the typedef. Fetching these
declarations can now be done with: .typedef("foo") or .class_("foo").

6. Add support for the future llvm 3.9. As in release v1.7.1, new structs and
typedefs are now exposed by llvm, which broke pyplusplus.
In this case these are __NSConstantString_tag and __NSConstantString.
The two declarations are now hidden from the declarations tree, but can still
be generated by using the config.flags = ["f1"] option.

7. Multiple fixes to adapt default arguments in functions for py++. Using the
latest version of CastXML is recommended. This makes sure default arguments
for function parameters are correctly defined, so that py++ can process them.

8. Fix for exception when using castxml + gcc5 + std=c++11 and maps.

9. Removed unittest2 dependency for testing with python 2.6

10. Testing: test with std::tr1 unordered containers for gcc >= 4.4.7 and castxml

11. Cosmetic fix for generator name printed to stdout when launching unit tests

12. Fix simple typo in example.py comment

Thanks to the following people for their contribution to this release:
Mark Moll, Ashish Sadanandan, Mark Oates

-------------

1. Fix exception in is_copy_constructor when the constructor's argument was
a typedef. is_copy_constructor will now return False instead of failing.
See issue 27.

2. Fix bug with utils.xml_generator being unset when reading cached file.
This could for example happen when reading a cached file from a second
python interpreter (e.g. in a subprocess or by calling pygccxml
multiple times from a script). See issue 27.

3. SafeConfigParser is throwing a deprecation warning in python 3.2 and newer.
Use ConfigParser instead. Thanks to Mark Moll for the patch.

4. Add support for cflags property in config files.
Thanks to Mark Moll for the patch.

-------------

1. Remove the __va_list_tag declaration from the tree when parsing with CastXML

The __va_list_tag declarations are internal declarations, which are often
not needed. They are for example polluting the declarations tree when running
pyplusplus.

This is optional but on by default. To still load the __va_list_tag declarations
in the tree, a config flag can be set like this: ``config.flags = ["f1"]``,
or by passing the ``flags=["f1"]`` argument the config setup.

2. Some code cleanup

3. Build new package for pypi. The ``1.7.0`` upload has gone wrong ...