On Thu, Dec 29, 2011 at 04:55:48PM +0100, Andreas Müller wrote: > I was wondering whether it is a good idea to use properties as to me > that seems very unlike the rest of the user-interface. > Also, from the documentation it is not entirely clear which attributes are > properties and which are not. Some of the properties have "read only" > in the comments, which is quite confusing when you didn't know it was > a property at all.
I feel like you: I'd rather avoid the use of properties. The reasons you give above are very good ones. Another reason is that they may hide expensive computation or memory copies. One reason to use properties is when doing 'interface adaptation', i.e. implementing an API with an object that doesn't fit well with this API. For me, it is pretty much the only valid use of properties: it's an impedance matching tool. My 2 cents, Gael ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
