pygccxml-development

[pygccxml-development] ssize_t in __convenience.pypp.hpp

[Matthias B. <ba...@ir...>]

I've just updated my version of Py++ (from r628 to the current revision) 
and now I get an error when I run the function transformer unit test:

In file included from function_transformations.cpp:12:
__convenience.pypp.hpp:22: error: no type `ssize_t' in `boost::python'


- Matthias -

Re: [pygccxml-development] ssize_t in __convenience.pypp.hpp

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

On 10/16/06, Matthias Baas <ba...@ir...> wrote:
> I've just updated my version of Py++ (from r628 to the current revision)
> and now I get an error when I run the function transformer unit test:
>
> In file included from function_transformations.cpp:12:
> __convenience.pypp.hpp:22: error: no type `ssize_t' in `boost::python'

What Boost.Python version do you use?


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

Re: [pygccxml-development] ssize_t in __convenience.pypp.hpp

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> On 10/16/06, Matthias Baas <ba...@ir...> wrote:
>> I've just updated my version of Py++ (from r628 to the current revision)
>> and now I get an error when I run the function transformer unit test:
>>
>> In file included from function_transformations.cpp:12:
>> __convenience.pypp.hpp:22: error: no type `ssize_t' in `boost::python'
> 
> What Boost.Python version do you use?

v1.33.1


- Matthias -

Re: [pygccxml-development] ssize_t in __convenience.pypp.hpp

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

On 10/16/06, Matthias Baas <ba...@ir...> wrote:
> v1.33.1

I am using "current cvs" and this is explains the problem. Is this an
option to switch
to "current cvs"? It contains a lot of fixes.

Any way the type is defined here:

http://boost.cvs.sourceforge.net/boost/boost/boost/python/ssize_t.hpp?view=log

Take a look on revision 1.1 comment. This is why I switched from int to ssize_t.
I will think about work around to the problem. You are welcome to
propose your solution
too.


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

Re: [pygccxml-development] ssize_t in __convenience.pypp.hpp

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> On 10/16/06, Matthias Baas <ba...@ir...> wrote:
>> v1.33.1
> 
> I am using "current cvs" and this is explains the problem. Is this an
> option to switch to "current cvs"? It contains a lot of fixes.

I'd rather postpone that until I really have to upgrade. It's quite a 
bit of work to do so (as I would have to compile & install it for 
several OSs and Python versions).

> I will think about work around to the problem. You are welcome to
> propose your solution too.

I'm not sure how this is best dealt with. I have too little experience 
with that (and I don't have a 64bit machine available). I suppose 
whatever "automatic" solution we choose there should probably also be a 
way for the user to override this mechanism and manually provide the 
type he'd like to use.

- Matthias -

Re: [pygccxml-development] ssize_t in __convenience.pypp.hpp

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

On 10/16/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > On 10/16/06, Matthias Baas <ba...@ir...> wrote:
> >> v1.33.1
> >
> > I am using "current cvs" and this is explains the problem. Is this an
> > option to switch to "current cvs"? It contains a lot of fixes.
>
> I'd rather postpone that until I really have to upgrade. It's quite a
> bit of work to do so (as I would have to compile & install it for
> several OSs and Python versions).
>
> > I will think about work around to the problem. You are welcome to
> > propose your solution too.
>
> I'm not sure how this is best dealt with. I have too little experience
> with that (and I don't have a 64bit machine available). I suppose
> whatever "automatic" solution we choose there should probably also be a
> way for the user to override this mechanism and manually provide the
> type he'd like to use.

I don't understand why, it seems to me that Python API forces us to use
some concrete type. I will check that, for a while I think it should be okay to
use int instead of ssize_t.
( I don't have time to investigate and solve this problem :-( )
I committed simple patch that temporally fix the problem
-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/