Compromise = 120 Columns

My main issue with 80 column split:

Modern IDEs provide some kind of Tab Completion like capability which
lessons the pain of writing out (reasonably) long descriptive variable and
function names (which everyone should be doing). When your using these
longer names you end up splitting very simple lines at 80 columns, and it
ends up reducing readability.

This is an obviously contrived example, but I have run into this very issue
with 80 column limits and long variable/function names (mostly crops up due
to nesting).

void raise_importance(const listType lessImportantThingList, const
VariableTypeForImportantThings somethingImportant)
{
    for(auto lessImportantThing(lessImportantThingList.begin());
        lessImportantThing == lessImportantThingList.end();
        lessImportantThing++)
    {
        if (somethingImportant == lessImportantThing)
        {
            VariableTypeForImportantThings moreImportantThing =
make_more_important(lessImportantThing);
        }
    }
}

So the function definition portion can be easily wrapped, but even then in
this example the end of the line is sitting at 79 characters, if it was a
templated type of some kind it would get harry quickly.

The line in the if can't be logically split to 80 characters in a readable
way, following most line split methods.

These are the 80 character issues I have run into. Yes they can happen with
anything less than infinite line length, but they are highly likely to
happen at 80, much less so I've found at 120.

On Thu, Jun 11, 2015 at 6:32 AM Owen Williams <owilli...@mixxx.org> wrote:

> So we have people who prefer 80 columns, and people who prefer unlimited
> columns.  There's not really a compromise position between these two
> options, so how do we choose?
>
>
> On Wed, 2015-06-10 at 09:28 -0400, Owen Williams wrote:
> > On Wed, 2015-06-10 at 09:16 -0400, RJ Ryan wrote:
> > >
> >
> > >
> > >
> > > The part of clang-format which frees you from having to talk about
> > > code style is that there is only one right way to format the code.
> > > Letting the developer have any choice in the matter goes against this.
> > >
> >
> > Agree.  I don't really feel strongly about line length, so 80 is fine
> > with me.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> > http://mixxx.org
> >
> >
> > Mixxx-devel mailing list
> > Mixxx-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mixxx-devel
> >
> >
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
------------------------------------------------------------------------------
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to