We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
That's not industry standard. H4D1 is correct. The way you have it gets really ugly and hard to read, so I would recommend you follow H4D1's recommendation; It could save you a lot of frustration.
I agree, H4D1 is right. Properly indented code is more readable and maintainable. Now as far as standards are concerned, the classic The C Programming Language (Ansi C Version) by Kernighan and Ritchie recommends H4DH1's style.
It's not "industry" standard: it is language, company, and - sometimes - even product influenced (notice I didn't say determined). The spacing of a language's brackets is entirely preference-based, even if coding conventions are encouraged by documentation (such as MSDN, Oracle, etc.). I've seen some bad stylings in my short time as a programmer.
This is actually worse and should not be an industry standard, this is how you get whats called "spaghetti code" because havign a lot of lines in this fashion will just look to jumbled and harder to debug.
A Very Big Sum
You are viewing a single comment's thread. Return to all comments →
well, H4DH1 Although it might be your personal preference but the way
{not like
That's not industry standard. H4D1 is correct. The way you have it gets really ugly and hard to read, so I would recommend you follow H4D1's recommendation; It could save you a lot of frustration.
I agree, H4D1 is right. Properly indented code is more readable and maintainable. Now as far as standards are concerned, the classic The C Programming Language (Ansi C Version) by Kernighan and Ritchie recommends H4DH1's style.
Using regular English makes MY life easier. Yet another 'standard' I would like everybody to follow.
It's not "industry" standard: it is language, company, and - sometimes - even product influenced (notice I didn't say determined). The spacing of a language's brackets is entirely preference-based, even if coding conventions are encouraged by documentation (such as MSDN, Oracle, etc.). I've seen some bad stylings in my short time as a programmer.
This is actually worse and should not be an industry standard, this is how you get whats called "spaghetti code" because havign a lot of lines in this fashion will just look to jumbled and harder to debug.
"Spaghetti code" refers to the look of the dependency graph, not the code.