Code style
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
I always do the latter. Seems more readable and all.
Quantum materiae materietur marmota monax si marmota monax materiam possit materiari?
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
I hate, really hate the first version ... I usually re-align all code with
{on the same line as function names or conditions ( if, while, ... ) anyway ... this is a religion topic ...
Maximilien Lincourt Your Head A Splode - Strong Bad
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
-
-
-
Oh gee, go ahead, spoil another fine debate about braces, brackets, and indentation. }~ ;););) Best, Jerry
The only way of discovering the limits of the possible is to venture a little past them into the impossible.--Arthur C. Clark
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
I know that a few publishers (magazine and book) want format #1 when you submit code snippets for an article or for the book. This helps cut down space used by the article and space in a magazine means $$$$. I use format #2 myself, but like it was mentioned before, the coding standards of the company that you are doing work for are what should be followed. Alot of companies that I have seen don't list this in their standards because of the style wars over this type of thing. I had a technician working for me years ago that used to take printouts and then get a ruler and draw red lines to connect the braces to make it easier for him to see. Of course this means that format #1 would be alot harder for him to figure out. Steve Maier, MCSD MCAD
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
Yes it takes a bit more space but I prefer the second style. PS Indentation ?
private void foo() { [tab here] //statements };P The tigress is here :-D -
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
The first version is only used by one person where I work. I've used the latter version for as long as I have used a language with curly braces (I started coding in C++ 12 years ago) and have never used anything else.
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
-
You didn't realise that there isn't actually a SQL backend, it's actually me hand-typing all responses to page requests? That's why page view times can be a little long if I'm tired, and why forums can get unthreaded if it's a Friday night and I've been on the turps. Hey - it seemed cheaper than trying to pay for SQL licences... cheers, Chris Maunder
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
private:
void foo()
{
//statements
}Company standard. Felt strange at first, but I got used to it, and now I use it everywhere
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
The first version is only used by one person where I work. I've used the latter version for as long as I have used a language with curly braces (I started coding in C++ 12 years ago) and have never used anything else.
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
I used the first style for 7 years in C++. I have been using the second style for almost 3 years in C#. With both styles I have and will continue making money. If someone pays me to do it one way or another, I will do it the way he wants it as long as he pays me my rate. Is not that what matters? The same goes for languages. I can write in Java, Visual Basic, C++, or C#. If you pay me, you choose the language and coding standards. Regards, Carlos H. Perez.
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
Are you trying to start a flame war in the lounge? ;) [edit]I agree with you :)[/edit] -- Denn du bist, was du isst! Und ihr wisst, was es ist! Es ist mein Teil...?
-
private:
void foo()
{
//statements
}Company standard. Felt strange at first, but I got used to it, and now I use it everywhere
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
Ick! Don't you get dizzy with the curly's aligned with the statements? It reminds me of the style a teacher of mine used:
if(x) {
// statements
}(He did it that way because he didn't have an autoindenting editor, and he was lazy. He never admitted it, but I know his character. And yeah, he hacked code when I was still breast feeding. :rolleyes:) -- Denn du bist, was du isst! Und ihr wisst, was es ist! Es ist mein Teil...?
-
You didn't realise that there isn't actually a SQL backend, it's actually me hand-typing all responses to page requests? That's why page view times can be a little long if I'm tired, and why forums can get unthreaded if it's a Friday night and I've been on the turps. Hey - it seemed cheaper than trying to pay for SQL licences... cheers, Chris Maunder
Working 9 to 5 would be holiday for you, wouldn't it? ;) -- Denn du bist, was du isst! Und ihr wisst, was es ist! Es ist mein Teil...?
-
i've been chatting with the new guy at work today and he respectfully informs me he can't recall the last time he saw this notation: private void foo() { //statements } and contends that almost always people use: private void foo() { //statements } which to me is a total waste of a linebreak and less readable. worse still, the other new dude concurs? whassup with that? being a fan of the former notation, it seems to me that either the new generation of coders are being being taught different, or the old ones are getting too anal about space. my question is... what in fact is the standard? perhaps we should have a poll on CodeProject and settle this once and for all!
lotuspro wrote: waste of a linebreak If coding style was about saving line breaks you would have a point. There is no standard, though the latter is seen far more frequent than the former, at least for functions and structs. House rules: If an inline function fits on one line, it can go on one line. Otherwise, classes, functions, structs always as version 2. if, for etc. is up to the coder.
we are here to help each other get through this thing, whatever it is Vonnegut jr.
sighist || Agile Programming | doxygen -
Yes it takes a bit more space but I prefer the second style. PS Indentation ?
private void foo() { [tab here] //statements };P The tigress is here :-D -
Ick! Don't you get dizzy with the curly's aligned with the statements? It reminds me of the style a teacher of mine used:
if(x) {
// statements
}(He did it that way because he didn't have an autoindenting editor, and he was lazy. He never admitted it, but I know his character. And yeah, he hacked code when I was still breast feeding. :rolleyes:) -- Denn du bist, was du isst! Und ihr wisst, was es ist! Es ist mein Teil...?
Frankly, I don't care. It is a matter of habit, anyway. Noone can convince me one style has any particular advantages over another.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
private:
void foo()
{
//statements
}Company standard. Felt strange at first, but I got used to it, and now I use it everywhere
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.