Re: [pygccxml-development] bug detecting read_only variables

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

On 3/10/07, Allen Bierbaum <al...@vr...> wrote:
> I think I may have just found a corner case for the auto-detection of
> which exposed class variables should be read_only.  I am wrapping a
> class that has a static member variable of a type that does not have an
> op=.  I think the idea the class designers had is that this would keep
> someone from assigning to these variables after they are created.
>
> Unfortunately py++ does not detect this case right now and tries to
> expose this variable using def_readwrite instead of def_read.  I think
> this could be fixed by adding some logic to
> variable_wrapper.variable_t.__find_out_is_read_only to check for this case.

Thank you, I will take a look on this issue

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