No your line is too long.
-
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.
-
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.
Not just no but hell no!
As the aircraft designer said, "Simplicate and add lightness". PartsBin an Electronics Part Organizer - Release Version 1.3.0 JaxCoder.com Latest Article: SimpleWizardUpdate
-
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.
At most one line that length. Try a smaller font -- I use 8pt. I also try to limit my line lengths to 112 characters. I used to use VT screens set to 132 characters per line. 132 characters per line ought to be enough for anybody.
-
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.
Obviously, this person has never seen how Microsoft writes long lines. For example,
HRESULT Scene::CreateDeviceDependentResources()
{
HRESULT hr = m_pRenderTarget->CreateSolidColorBrush(
D2D1::ColorF(1.0f, 1.0f, 0),
D2D1::BrushProperties(),
&m_pFill
);if (SUCCEEDED(hr)) { hr = m\_pRenderTarget->CreateSolidColorBrush( D2D1::ColorF(0, 0, 0), D2D1::BrushProperties(), &m\_pStroke ); } return hr;}
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak
-
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 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
-
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.
My first job was in an age where graphic terminals were just starting to appear. My employer were designing a screen management library, primarily oriented towards screens with a resolution of 80 by 25 characters. Yet, we wanted the library to be prepared for the graphics of the future. We had a brainstorming to provide input to the requirements spec, coming up with a proposal where the screen could be filled by a sphere. On this globe, you could allocate several virtual screens, as a sector of a given number of degrees from pole to pole. Each virtual screen (i.e. sector) could scroll independently of the others, and you could spin the globe to bring a specific screen towards you. We never agreed which would be the better default: Either, to clip the contents to the 'longitude' edges of the virtual screen (so that you would have to scroll a line to the middle to see its full length), or to scale down towards the poles (so that you would have to scroll to see a line in maximum size). For some reason, this solution has never been realized (to my knowledge). I am quite sure that it would be possible with Linux and this screen driver. There must be someone who thinks that this is a great idea. (In case you wonder: We were not dead serious about it - it was in the same class as 'esoteric' programming languages such as brainfuck or whitespace.)
Religious freedom is the freedom to say that two plus two make five.
-
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.
Get a bigger monitor? Learn how to use a line continuation character maybe? (depending on language options) The only really long lines I ever have are sql queries. In the past, I used to insist on keeping the Select From Group By, and Order By on individual lines and concatenate. Nowadays, I either use line continuations or a string builder to keep everything visible. (horizontally)
"Go forth into the source" - Neal Morse "Hope is contagious"
-
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 find that dots and commas and such are easier to see at the start of a line. I put commas and binary operators (not dots) on their own lines in many cases so they really stand out.
-
Get a bigger monitor? Learn how to use a line continuation character maybe? (depending on language options) The only really long lines I ever have are sql queries. In the past, I used to insist on keeping the Select From Group By, and Order By on individual lines and concatenate. Nowadays, I either use line continuations or a string builder to keep everything visible. (horizontally)
"Go forth into the source" - Neal Morse "Hope is contagious"
When our coding standards were revised, the working group proposed to limit line lengths 72 characters of code. Our project manager immediately granted an exemption to this rule: We also had rules for how to make up names for #define constants (identifying module, submodule, function etc. etc.) that resulted in constant names exceeding 80 chars. (Personally, I think that rules that can lead to such results are completely crazy. There are also rules for how to name directories, subdirectories, sub-sub and sub-sub-sub-... directories, so that any directory should be 'self-identifying' even if located in an identifying higher directory. In one case, I counted the same module ID repeated seven times in a complete path string. This naming standard obviously created problems for DOS-friendly file systems with a maximum path length of 260 characters. Even if that 260 char limit sometimes was a pain in the horse, I think that naming rules frequently leading to path strings filling several lines of output are just as crazy!)
Religious freedom is the freedom to say that two plus two make five.
-
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.
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.
-
Obviously, this person has never seen how Microsoft writes long lines. For example,
HRESULT Scene::CreateDeviceDependentResources()
{
HRESULT hr = m_pRenderTarget->CreateSolidColorBrush(
D2D1::ColorF(1.0f, 1.0f, 0),
D2D1::BrushProperties(),
&m_pFill
);if (SUCCEEDED(hr)) { hr = m\_pRenderTarget->CreateSolidColorBrush( D2D1::ColorF(0, 0, 0), D2D1::BrushProperties(), &m\_pStroke ); } return hr;}
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak
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.
-
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.
