4 ms·
I've seen code where 20-odd characters were taken up by whitespace. Of course, at that point, you really want to split it out into different, named functions...
by vertex-four 10y ago
I've seen code where 20-odd characters were taken up by whitespace. Of course, at that point, you really want to split it out into different, named functions... code like that is unreadable for entirely different reasons than line lenth. Similar things the case for almost every single case where a line might become "too long" - I don't think the length is actually the issue so much as the complexity.
- andrey_utkin 10y agobut "20-odd" (let it be 24) is just 3 * 8, which is something like this. I don't see how this is already screwed up for complexity. class A { A::a() { if (expr) { do1(); } else { do2(); } } }
- zokier 10y agoI think most people have converged to 4 space tabstops, so 24 spaces means 6 levels of indentation.
- sixothree 10y agoNamespace, class, method, loop, conditional brings us to 20.
- vertex-four 10y agoI don't actually know of any project which uses 6 or 8 characters per indentation level.
- andrey_utkin 10y ago8 chars is default tab size. So e.g. "git diff" shows you 8-position tabs. Github (and Bitbucket, etc.) diff visualizer also shows it as 8 positions. Any editor should use 8 by default, too. And, believe me or not my space-loving friends, tab-indented codebases still exist.
- vertex-four 10y agoMy editor definitely puts tabstops at 4. Weird.
- khedoros 10y agoMy first change to any editor is to set tabstops at 4 characters. That's the standard policy at my employer, and I like it for my own projects, as well.