On Mon, 2008-10-27 at 10:13 +0100, Dirk Meyer wrote: > I did not like monitoring(bool) and neither do I like monitor(bool). I
I don't like monitoring(bool) either, but monitor(bool) seems fine. And if nobody is likely to want to disable monitoring, then monitor(bool=True) seems better. > don't know, it feels better with monitor = bool. If using a functions is > better than a property because the setter does complex stuff, I woul Well, like I said, it's not an exact science. Property setters will almost certainly have side-effects, it's just a judgement call as to when they are complex enough to merit the more explicit approach of a method. It's insidious when attr=foo is very expensive (or maybe even blocks for a little bit). It's beacon, so it's up to you. If you think the side-effects monitor=True are subtle enough to justify a property, then ok. I just want us to start thinking about it so we don't abuse properties too much. Jason. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
