Hey there guys, attached is the elementary OS coding style (We have this on
a Google Doc, but the formatting is broken on it, so I'm rewriting it with
Writer to then port to Google Docs again).
I want to add an exception regarding the space character before opening
parentheses, and I want to know
I agree that we should have consistency but at this level just seems
unproductive and a wast of time...
I think the things that really make a difference in this situations are
in cases like:
if(condition){
}
vs
if(condition)
{
}
or in functions:
return_type
func_name(param, param) {
}
vs
All those cases have been handled. It took less time for us to decide that
this exception is a +1 than it took you to write that post, I don't think
this is a waste of time.
On Thu, Sep 13, 2012 at 5:40 PM, Darcy Brás da Silva
dardeve...@cidadecool.com wrote:
I agree that we should have
IMHO we should keep the style comprehensible and easy to remember. Maybe
that way we'll manage to actually follow it.
If you're willing to put a lot of time into developing the coding style, I
can suggest reading the relevant Code Craft chapter first (I can lend a
copy of the book if you don't
Not that I do a lot of coding, but I'm +1 on the (( exception. It looks much
more readable imho.
On Thu, Sep 13, 2012 at 10:45 AM, Sergey Shnatsel Davidoff
ser...@elementaryos.org wrote:
IMHO we should keep the style comprehensible and easy to remember. Maybe that
way we'll manage to actually
5 matches
Mail list logo
