Ian Bicking wrote: > Guido van Rossum wrote: >> On 12/14/05, Barry Warsaw <barry at python.org> wrote: >> >>>On Thu, 2005-12-15 at 11:13 +1100, Dave Cole wrote: >>> >>> >>>>The only thing I strongly disagree with is the promotion of javaNaming >>>>to equal footing with python_naming. >>> >>>Actually, they're not on equal footing atm. I happen to agree with you >>>though. >> >> >> It doesn't matter. Many large projects are adopting the camelCase >> convention, either by choice or by accident. I did a brief review of >> Zope 3 and Chandler, and while neither is consistent, camelCase >> prevails (Chandler also has a lot of CapWords method names, wihch >> suggests they didn't get this from Java -- maybe from C++?). > > Everything that touches wx seems to adopt CapWords method names -- in > part (hopefully) or in whole. Wx's API comes from Windows, and the > Microsoft method conventions. Bad, that. While the Windows API names once made sense when they referred to standalone functions, not methods, they now look ugly in wx or .NET. Reinhold -- Mail address is perfectly valid!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4