pygccxml-development

[pygccxml-development] A way to turn off indexing suite?

[Allen B. <al...@vr...>]

Is there a way to disable the new code that automagically generated 
indexing suite wrappers?  It has broken all my modules where I used to 
do this manually and the generated code says it can't compile anyway.  
How can I remove it?

-Allen

Re: [pygccxml-development] A way to turn off indexing suite?

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

On 6/22/06, Allen Bierbaum <al...@vr...> wrote:
> Is there a way to disable the new code that automagically generated
> indexing suite wrappers?

I just committed some changes that allow this.

mb.build_code_creator( ..., enable_indexing_suite=False )

> It has broken all my modules where I used to
> do this manually and the generated code says it can't compile anyway.

If I understand you right, the manual code that you added worked okay, but
code generated by py++ is not? What do you mean "It has broken all my
modules where I used to do this manually"? May be you find a bug? Do
you care to explain?

Thanks

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

Re: [pygccxml-development] A way to turn off indexing suite?

[Allen B. <al...@vr...>]

Roman Yakovenko wrote:

>On 6/22/06, Allen Bierbaum <al...@vr...> wrote:
>  
>
>>Is there a way to disable the new code that automagically generated
>>indexing suite wrappers?
>>    
>>
>
>I just committed some changes that allow this.
>
>mb.build_code_creator( ..., enable_indexing_suite=False )
>
>  
>
>>It has broken all my modules where I used to
>>do this manually and the generated code says it can't compile anyway.
>>    
>>
>
>If I understand you right, the manual code that you added worked okay, but
>code generated by py++ is not? What do you mean "It has broken all my
>modules where I used to do this manually"? May be you find a bug? Do
>you care to explain?
>  
>
The combination of code generated manually and automatically now tries 
to register the same class twice which makes boost.python assert.  Also 
the generated code has a comment that says it should not compile.  This 
worries me because it does compile.  But for now since the old manual 
code works I would rather just keep using it until I have time to learn 
how to use the indexing suite support in pypp.

-Allen

>Thanks
>
>  
>

Re: [pygccxml-development] A way to turn off indexing suite?

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

On 6/22/06, Allen Bierbaum <al...@vr...> wrote:
> Also
> the generated code has a comment that says it should not compile.  This
> worries me because it does compile.

You don't have to worry. This is new functionality and I think I have bug. The
comment says that py++ can not find operator==, right. If the code compiles
than your class do has operator==. Can you contribute the test case, so I can
find and fix the bug.

> But for now since the old manual
> code works I would rather just keep using it until I have time to learn
> how to use the indexing suite support in pypp.

If it works, don't touch! :-)

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

Re: [pygccxml-development] A way to turn off indexing suite?

[Allen B. <al...@vr...>]

Roman Yakovenko wrote:

>On 6/22/06, Allen Bierbaum <al...@vr...> wrote:
>  
>
>>Also
>>the generated code has a comment that says it should not compile.  This
>>worries me because it does compile.
>>    
>>
>
>You don't have to worry. This is new functionality and I think I have bug. The
>comment says that py++ can not find operator==, right. If the code compiles
>than your class do has operator==. Can you contribute the test case, so I can
>find and fix the bug.
>  
>
I don't have an easy way to get a test case out of this one but I will 
try to look into it.

On a related note, I took your advice and I am keeping track of any 
issues, missing features, problems, etc I run into while porting some 
projects to use pyplusplus.  My list is getting pretty long.  Once I get 
done with the porting I promise that I will send out an e-mail with a 
description of the things I have run into.

>  
>
>>But for now since the old manual
>>code works I would rather just keep using it until I have time to learn
>>how to use the indexing suite support in pypp.
>>    
>>
>
>If it works, don't touch! :-)
>  
>
Exactly.  Especially when trying to meet deadlines. :)

-A