No your line is too long.
-
Well, the fact that only Linux supports diagonal orientation says something about the person wanting diagonal orientation. "Too busy seeing if they COULD do it to be bothered with whether they SHOULD do it."
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
From CP newsletter https://www.codeproject.com/News.aspx?ntag=19837497829658814&_z=2928472[^] They want to run their monitors in a diagonal mode because? "Why 22 degrees? At that angle, you get the longest line length (stretching between opposite corners)" My answer to that - your line is too long. Make it shorter. You are not writing code for you but are writing it for the people in the future that must maintain it.
I hate long lines. On the show Supernatural the acting head of hell (Satan was otherwise locked up) decided that since inevitably some people enjoyed the various tortures dished out that he would make everyone stand in line for eternity. "Nobody likes waiting in line"
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
In Norwegian slang, 'slanted' is a term for homosexual. Are you referring to something like that? I wasn't aware of any similar slang term in English.
Religious freedom is the freedom to say that two plus two make five.
No, I meant the actual tilted monitor. Some Linux users are elitist looking down their noses at other operating systems, so being able to have a tilted monitor could be another example.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
From CP newsletter https://www.codeproject.com/News.aspx?ntag=19837497829658814&_z=2928472[^] They want to run their monitors in a diagonal mode because? "Why 22 degrees? At that angle, you get the longest line length (stretching between opposite corners)" My answer to that - your line is too long. Make it shorter. You are not writing code for you but are writing it for the people in the future that must maintain it.
to each her own . as for me i utilize word wrap . rules ? nonsense . my one and only rule is it must be easy to understand but no easier .
-
I hate long lines. On the show Supernatural the acting head of hell (Satan was otherwise locked up) decided that since inevitably some people enjoyed the various tortures dished out that he would make everyone stand in line for eternity. "Nobody likes waiting in line"
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
to each her own . as for me i utilize word wrap . rules ? nonsense . my one and only rule is it must be easy to understand but no easier .
A long time ago, I read about a study - in a printed periodical, so no URL - where a number of test persons were split into two groups and given the same source code to study. One group got it laid out like ordinary prose, the way you would write a plain text? ("If the rain stops, let's go to the beach. Otherwise, let's break a bottle of wine!" in a single line). The other group got the same program laid out "the programming way", with conditions, if- and else-clauses on separate lines, with proper indentations etc. Similar for loops and other constructs. After the test persons had been given a controlled amount of time to study the code, they were to fill in a questionnaire to reveal how well they had understood the program logic. It turned out that those who had read the "prose formatted" program code scored significantly higher than those who had been reading the "program structured" layout. This is so many years ago that the average person still could be expected to read both fiction and non-fiction books. Today, lots of young people never read a novel after the Harry Potter books (which they chose when school required them to pick one novel to read). So maybe the results would be different today, with lots of people inexperienced with extracting meaning unless it is conveyed both in text, semantics highlighted with punctuation and structure mediated through blocks and indentation.
Religious freedom is the freedom to say that two plus two make five.
-
No, I meant the actual tilted monitor. Some Linux users are elitist looking down their noses at other operating systems, so being able to have a tilted monitor could be another example.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
honey the codewitch wrote:
I hate long lines.
So you prefer macaroni to spaghetti? :-)
Religious freedom is the freedom to say that two plus two make five.
as for me i prefer fettuccini (rice even rather than whole wheat . refined wheat never .)
-
No, I meant the actual tilted monitor. Some Linux users are elitist looking down their noses at other operating systems, so being able to have a tilted monitor could be another example.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
They think they're looking down, but they are actually looking up.
-
A long time ago, I read about a study - in a printed periodical, so no URL - where a number of test persons were split into two groups and given the same source code to study. One group got it laid out like ordinary prose, the way you would write a plain text? ("If the rain stops, let's go to the beach. Otherwise, let's break a bottle of wine!" in a single line). The other group got the same program laid out "the programming way", with conditions, if- and else-clauses on separate lines, with proper indentations etc. Similar for loops and other constructs. After the test persons had been given a controlled amount of time to study the code, they were to fill in a questionnaire to reveal how well they had understood the program logic. It turned out that those who had read the "prose formatted" program code scored significantly higher than those who had been reading the "program structured" layout. This is so many years ago that the average person still could be expected to read both fiction and non-fiction books. Today, lots of young people never read a novel after the Harry Potter books (which they chose when school required them to pick one novel to read). So maybe the results would be different today, with lots of people inexperienced with extracting meaning unless it is conveyed both in text, semantics highlighted with punctuation and structure mediated through blocks and indentation.
Religious freedom is the freedom to say that two plus two make five.
They probably require that it be read to them while they do pilates.
-
From CP newsletter https://www.codeproject.com/News.aspx?ntag=19837497829658814&_z=2928472[^] They want to run their monitors in a diagonal mode because? "Why 22 degrees? At that angle, you get the longest line length (stretching between opposite corners)" My answer to that - your line is too long. Make it shorter. You are not writing code for you but are writing it for the people in the future that must maintain it.
Wrap baby, wrap (rather than Burn baby, burn)
Paul Sanders. If I had more time, I would have written a shorter letter - Blaise Pascal. Some of my best work is in the undo buffer.
-
From CP newsletter https://www.codeproject.com/News.aspx?ntag=19837497829658814&_z=2928472[^] They want to run their monitors in a diagonal mode because? "Why 22 degrees? At that angle, you get the longest line length (stretching between opposite corners)" My answer to that - your line is too long. Make it shorter. You are not writing code for you but are writing it for the people in the future that must maintain it.
Diagonal mode wastes so much real estate with these triangles at the edges of the monitor. It just makes zero sense. And the conclusion that 22 degrees is the optimal angle is also not backed by any proof. AFAIR the article just said that "it was researched", which was.. weird.
-
I can understand the motivation. I've seen, and perhaps perpetrated, something like:
string someString = mything.something().somethingElse().foo().bar().bang().whiz().toString()
Which can sometimes lead to very long lines. But any decent optimizer should be able to elide otherwise unused intermediate object so maybe
auto something = mything.something();
auto foobar = something().foo().bar();
auto whiz = foobar().bang().whiz();
string someString = whiz.toString();is preferable? But if you're going to keep the long version as a single statement, but write it over separate lines do you prefer putting the . at the end or the start of the line? e.g
mything.something().
foo().bar().whiz().
bang().toString()vs
mything.something()
.foo().bar().whiz()
.bang().toString()"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
-
string someString = mything
.something()
.somethingElse()
.foo()
.bar()
.bang()
.whiz()
.toString()
;I like that look. I try to write my SQL like that but have been leaving the dot-separators on the previous line in code. My thinking was to indicate that the line (command) was not yet finished. With this style, keeping each line short it is clear that each line is a continuation. With SQL, I have been cheating on that style to keep like fields on a single line: ... , fKey , LastName, FirstName, MidName , AddrLine1, AddrLine2, City, State, Country, Zip --, foo , bar ...
-
I hate long lines. On the show Supernatural the acting head of hell (Satan was otherwise locked up) decided that since inevitably some people enjoyed the various tortures dished out that he would make everyone stand in line for eternity. "Nobody likes waiting in line"
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I have zero problem with that. In fact, I'd much rather see a function's parameters being broken by parameter (one per line) rather than 3 on the first line, 2 on the second line, then 4 on the third line, etc. If it has to be broken down, go all the way. Then if a parameter consists of a function call, and that function needs so many parameters of its own that that line becomes long, then break it into multiple lines too, with an extra indentation level. Seems so logical to me.
-
I can understand the motivation. I've seen, and perhaps perpetrated, something like:
string someString = mything.something().somethingElse().foo().bar().bang().whiz().toString()
Which can sometimes lead to very long lines. But any decent optimizer should be able to elide otherwise unused intermediate object so maybe
auto something = mything.something();
auto foobar = something().foo().bar();
auto whiz = foobar().bang().whiz();
string someString = whiz.toString();is preferable? But if you're going to keep the long version as a single statement, but write it over separate lines do you prefer putting the . at the end or the start of the line? e.g
mything.something().
foo().bar().whiz().
bang().toString()vs
mything.something()
.foo().bar().whiz()
.bang().toString()"A little song, a little dance, a little seltzer down your pants" Chuckles the clown
-
I like that look. I try to write my SQL like that but have been leaving the dot-separators on the previous line in code. My thinking was to indicate that the line (command) was not yet finished. With this style, keeping each line short it is clear that each line is a continuation. With SQL, I have been cheating on that style to keep like fields on a single line: ... , fKey , LastName, FirstName, MidName , AddrLine1, AddrLine2, City, State, Country, Zip --, foo , bar ...
bryanren wrote:
SQL like that but have been leaving the dot-separators on the previous line in code.
lol ... Really not obvious to me what you meant until I got to your example. I was crunching my brain trying to find when one would have multiple periods. Yes I use exactly that form for SQL also. Unlike with other expressions and even with parameters in C#/Java I still tend (always?) to put the comma at the end of the line rather than the beginning. No real reason although I could state that a comma is not part of an expression. But then I do it that way for SQL. So no way I can justify it.
-
No, I meant the actual tilted monitor. Some Linux users are elitist looking down their noses at other operating systems, so being able to have a tilted monitor could be another example.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
Diagonal mode wastes so much real estate with these triangles at the edges of the monitor. It just makes zero sense. And the conclusion that 22 degrees is the optimal angle is also not backed by any proof. AFAIR the article just said that "it was researched", which was.. weird.