Re: [pygccxml-development] Finalizing a class?

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

Roman:

Was there ever any progress on this?  I am back to wrapping my original 
library now and I really need the ability to finalize classes.

-Allen

Roman Yakovenko wrote:

> On 5/17/06, Allen Bierbaum <al...@vr...> wrote:
>
>> Roman Yakovenko wrote:
>>
>> > On 5/17/06, Allen Bierbaum <al...@vr...> wrote:
>> >
>> >> This seems like something that should be made easier for the user.
>> >>
>> >> Perhaps something like:
>> >>
>> >> my_ns.class_("ClassA").finalize()
>> >>
>> >> class_a.member_function("my_method").finalize()
>> >>
>> >> Is there any reason pyplusplus can't provide a more simple interface
>> >> like this for the user?
>> >
>> >
>> > What should do pyplusplus if the only way to export declaration is to
>> > create some
>> > wrapper for it? For example class with pure virtual function:
>> >   raise an error?
>> >   create wrapper?
>> >   try to export without wrapper and let to the user to understand
>> > what he did
>> >   wrong?
>>
>> I think it should raise an error and explain to the user why pyplusplus
>> can't honor their request.
>>
>> If it is ever possible to detect that they user is doing something that
>> is invalid and can be detected, then the system should tell the user and
>> ask them to correct it.
>
>
> It is not convinient, I think we should have next functionality:
> finalize if possible
>
>>  For example I would like the option to turn on
>> a warning or even error message for cases where pyplusplus knows the
>> user should specify a calling policy but hasn't.  The system already
>> puts a comment in the code to that effect, it may as well warn the user
>> as well.
>
>
> I will print a message to log.
>
>> -Allen
>>
>>
>
>