Re: [pygccxml-development] __int128_t traceback

[Roman Y. <rom...@gm...>]

On Tue, Jul 6, 2010 at 5:04 PM, Gustavo Carneiro <gjc...@gm...> wrote:
> It seems pygccxml (1.0) tracbacks when the type __int128_t is found in a
> header file.  I don't really care about the type, it is used internally by
> an implementation class which I do not wish to wrap, but the mere presence
> of this type is enough to crash pygccxml and stop me from scanning the rest
> of the API.

I understand.

We have few ways to continue:
* you create an xml file that contains that type and send it to me and
I fix pygccxml
* you can add that type to pygccxml by yourself and send me the patches :-)


Basically the are only few place, where pygccxml should be changed:
* declarations/cpptypes.py
  * Python class, that represents the type should be created and added
to the FUNDAMENTAL_TYPES dictionary
* declarations/type_traits.py
  * is_integral function should be changed to return "true" for this type too
* declarations/__init__.py
  * the file should provide access to the class

That's all. You are free to select any method you want :-)



-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/