This discussion is veering off into Bikeshedding.
I will now rescue it:
- A commit hook which formats source code on commit, is the ONLY way to
have a followed formatting policy.
Any other approach will result in nothing but bikeshedding, or worse, flame
wars.
best regards,
Jakob
On September 13, 2012 at 11:42 PM Daniel Fore <dan...@elementaryos.org> wrote:
> 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 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 have it handy).
>
> I can't +1 or -1 because I don't code in Vala, but in BASH and Python I use
> both "( (" and "((", depending on readability of the content. I wouldn't be
> able to keep all those little rules in mind, I guess.
>
> --
> Sergey "Shnatsel" Davidoff
> OS architect @ elementary
>
--
Mailing list: https://launchpad.net/~elementary-dev-community
Post to : elementary-dev-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~elementary-dev-community
More help : https://help.launchpad.net/ListHelp
