Re: [pygccxml-development] improving user experience
Brought to you by:
mbaas,
roman_yakovenko
From: Roman Y. <rom...@gm...> - 2006-07-17 17:58:27
|
On 7/17/06, Matthias Baas <ba...@ir...> wrote: > Roman Yakovenko wrote: > > Also I completely forgot about "readme" functionality. May be my > > approach is wrong. > > May be I need to change the code. I think, that instead of reporting > > warning from > > "ignore" property, I need to report it from module_creator/creator.py file. > > > > What do you think? > > Well, I have to admit that I actually was somewhat surprised to see the > __report_warning() message being invoked when accessing the "ignore" > property but then, as long as it works..... It was ugly hack, that does not work :-(. > But it does sound reasonable to me if problems are reported when the > code creator tree is created, so maybe this would make the code more clear. I agree. > By the way, when exactly is _exportable_impl() called 1. When pyplusplus asks for ignore property value. This is happen from code creators factory. ( That is why I introduced the hack ) 2. When user calls for readme method exportable property why_not_exportable property > (or when is the > exportable property accessed)? Would it also be an option to log a > warning message right at the place where it is created? (this is > probably what I would have done in the first place) You mean during construction, right? It is not possible. The main reason for this is that construction is done in 2 steps ( scanner and linker ) > Or is the generated message string used for something else as well? No. It's main purpose it to be printed to user. > Or is "exportable" already accessed somewhen before the user actually > ignored the declaration? (so that the message should not be printed) No. I don't think so, but we should be careful to not print same message ( from same declaration ) twice. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |