Re: [Sunuml-developers] Local source directories and the CamelCase topic
Status: Planning
Brought to you by:
lazaruslong
From: Doreen S. <nee...@gm...> - 2008-11-11 17:01:40
|
Hi, > > Mhhh... I read too fast. You really want to use mixedCase for classes? > I don't think that the mixedCase was meant to used for classes. Like I understand the last comments, all developers agree with the fact to use CamelCase for classes, right? I also agree with the compromise to "inherit" the standard of extended classes and use our own standard for clean new classes. > > PS: I always wonder why defining the coding style & project folder layout > takes so much time... and if the leader should impose it :/ > Steven, you have to decide such things because someone HAS TO decide. There are a lot of opinions and practises. But I think we all are willing to use any standard whatever would be established :) Define some standard and we will follow ... probably ... ;) Reeny -------- Original-Nachricht -------- > Datum: Tue, 11 Nov 2008 11:58:53 +1100 > Von: "Steven Gay" <laz...@gm...> > An: sun...@li... > Betreff: Re: [Sunuml-developers] Local source directories and the CamelCase topic > > > > I think that maybe a point in the middle will be better. > >> > >> - Use CamelCase methods when the class we make extends directly from a > >> wxPython class, because if you override methods from the upperclass you > >> are forced to use that standard, and I think all methods should have > the > >> same standard inside a class. This should be used for example on a > >> subclass of wx.Frame. > >> > >> - Use mixedCase standard when making our own classes and model classes. > >> I would prefer to use this standard everywhere but on the other classes > >> it would be prone to error mixing the standards. > > > > > > OK - I will wiki this. > > > > Mhhh... I read too fast. You really want to use mixedCase for classes? > > I will let you decide tell me when you all agree :) > > Just a comment. The fact that you are forced to use the CamelCase when > overridding mix well with the mixedCase standard as it identifies clearly > the methods that are overiding a base library versus our own methods. I > still don't see the advantage of the CamelCase approach but as I said: > tell > me when you agree for a style. > > PS: I always wonder why defining the coding style & project folder layout > takes so much time... and if the leader should impose it :/ > > Regards, > Steven -- GMX Download-Spiele: Preizsturz! Alle Puzzle-Spiele Deluxe über 60% billiger. http://games.entertainment.gmx.net/de/entertainment/games/download/puzzle/index.html |