> In Java, rather than properties, they have the JavaBeans naming > convention. According to this convention, getters are named getFoo() > -> foo, and setters are named setFoo(foo) -> void. In most of the > dotNet code I've seen, you can take Java (or SVG, or whatever system > they're imitating this month) and make it initCap (getFoo() becomes > GetFoo()). Since Jython treats the JavaBeans calling conventions as > properties, I assume IronPython is doing something similar. Although > in that case, you should be able to just write AllBooks rather than > GetAllBooks (although both ways might work).
Yes, I'm somewhat familiar with JavaBeans. It wasn't the naming conventions that bothered me so much, as using Get... but not making it a callable. I gather some more feedback. Not a high priority. > I think you should freely change the obvious typo, but not the code > unless you've tried to run it and found it does not actually work. I > don't have IronPython, or any intention to install or run it, so take > anything I say about it with a large grain of salt. > > --Dethe OK. Kirby _______________________________________________ Edu-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/edu-sig
