[cfe-dev] always break if params don't fit

[Tim W]

by the way ... here is one of the talks I've been talking about ... from
slide 20, 14.30 it is about argument alignment.

http://www.slideshare.net/Kevlin/seven-ineffective-coding-habits-of-many-programmers
    https://vimeo.com/97329157

I'm pretty sure I saw it first on ACCU but I can be wrong :?

Cheers,
Tim


An Apple a day keeps Windows away

ACCU - http://www.accu.org - Professionalism in Programming.

On Wed, May 13, 2015 at 8:28 PM, Tim W <timpie.w at gmail.com> wrote:

> Hi Daniel,
>
>
> >Refactoring and version system friendliness are concerns when writing
> code. clang-format's explicit goal is to make code readable.
>
> I don't really want to argue with you about this because that is also on
> top of my list and I also can understand that you don't want support
> every style nuance.
> But here is my view ... the first goal of this style is also
> readability.  For me proposal (3) from @mpark is less readable because
> it separates the arguments in head and tail and I would like to have
> them together and aligned.  As for the version control system ... it is for
> easily reading the history of the file and when I refactor the function
> name in example (3) its looks  in the history that all parameters are
> changed.  And yes we can turn on ignore whitespaces but then we will miss
> other whitespace changes.
>
> I also convinced myself that is a globally used style but that is probably
> because I have seen it in two presentation at ACCU about C++ code style :)
>
>
> Any hint of how I could implement it myself if it will never make it into
> the tool?
>
> Kind regards,
> Tim
>
>
>
> An Apple a day keeps Windows away
>
> ACCU - http://www.accu.org - Professionalism in Programming.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150513/3627686f/attachment.html>