|
From: Roman Y. <rom...@gm...> - 2006-09-11 19:05:44
|
On 9/11/06, Matthias Baas <ba...@ir...> wrote: > Oops, I wasn't aware that I broke that rule. Uhm, but what did I do that > actually broke it? I haven't used anything from pyplusplus (or other > external code). Yes I know, dummy_type_t was defined in pygccxml for convenience reason. > The only class that I've used is dummy_type_t which is defined within > pygccxml. And the behavior of the argument class was not changed, it was > just an addition so that the type argument can now also be a string. Any > existing code should continue to work as before. No. I have to fix some bug. But basically consider next case argument_t( 'x', type='const std::string&', ... ) No somewhere within the Py++ code there is ( it will be tomorrow ) a condition: if is_immutable( arg.type ): ... else: ... Well, it will fail and the bug is that Py++ did not meat user expectations. So, I prefer a user to know when he works with real type and when he works with dummy one. You can say ( and you will be right ) that I introduce some complexity to the user, but I think this is an important one. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |
