func( arg1, arg2 )

Sometimes.

2 (13.3%)

No.

9 (60%)

Yes.

4 (26.7%)

Total Members Voted: 9

[gibson042]

If you indent with tabs, then everyone can read your code in the presentation most comfortable for them.

Not necessarily. Consider this code, where \t represents a tab:

Code: [Select]

if (foo % 42 == pow(bar, 2) &&
\tfoo != baz)
{
\tprintf("whee!");
}

I would consider that code equally readable regardless of tab width.  Regardless, if alignment was so critical then it could have been written like so:

Code: [Select]

if (
\tfoo % 42 == pow(bar, 2) &&
\tfoo != baz)
{
\tprintf("whee!");
}
And don't talk to me about wasting lines; if that was important the code would have used 1TBS in the first place.  Another fix—although not one with my support—would use spaces for the continuing conditional and tabs for block indentation in something akin to KNF style.

[wtfk]

Tab is to confuse.  Joe uses 2 character tabs, Sam uses 4.  Sally uses 8 character tabs, Simon 3.  I use four spaces, and Joe, Sam, Sally and Simon can read my code.

If you indent with tabs, then everyone can read your code in the presentation most comfortable for them.

Spoken like someone who has never opened and tried to read someone else's code with different tab stop settings than his own.  Really, after 25 years, I do know what the fuck I'm talking about.

[MobileDigit]

#1USEFUCKINGWHITESPACE

Which is easier to read:
#1 USE FUCKING WHITESPACE
or,
# 1  U S E   F U C K I N G   W H I T E S P A C E
?

If you introduce extra spaces it makes it more difficult to scan.

[wtfk]

#1USEFUCKINGWHITESPACE

Which is easier to read:
#1 USE FUCKING WHITESPACE
or,
# 1  U S E   F U C K I N G   W H I T E S P A C E
?

If you introduce extra spaces it makes it more difficult to scan.

Sometimes special punctuation helps:

/********************************************************
***                                                   ***
***    U S E   F U C K I N G   W H I T E S P A C E    ***
***                                                   ***
*********************************************************/

[gibson042]

If you indent with tabs, then everyone can read your code in the presentation most comfortable for them.

Spoken like someone who has never opened and tried to read someone else's code with different tab stop settings than his own.  Really, after 25 years, I do know what the fuck I'm talking about.

If code is unreadable at your tab width (a problem I have never encountered after 15 years), you can change it to equal the author's and see the code exactly as it was written (the so-called benefit of spaces).  But tabs, unlike spaces, do not require that kind of viewing.

[wtfk]

If you indent with tabs, then everyone can read your code in the presentation most comfortable for them.

Spoken like someone who has never opened and tried to read someone else's code with different tab stop settings than his own.  Really, after 25 years, I do know what the fuck I'm talking about.

If code is unreadable at your tab width (a problem I have never encountered after 15 years), you can change it to equal the author's and see the code exactly as it was written (the so-called benefit of spaces).  But tabs, unlike spaces, do not require that kind of viewing.

What "kind" of viewing are you taking about?  I'm sort of addicted to being able to read the code I'm editing, and I don't particularly like spending 5 minutes interactively changing the tab widths then inspecting the code to see if it looks indented properly for each effing source file I open.  That's why virtually everyone I've worked with has gone from tabs to tabs-as-spaces.

[ladyattis]

On a side note, I hate it when some IDEs bury the fracking tab features so deep in the options selection that I just give up. Like with Netbeans or BlueJ, fracking hell!

-- Brede

[MobileDigit]

Sometimes special punctuation helps

func( arg1, arg2 ) is not special, it is common.

[wtfk]

Sometimes special punctuation helps

func( arg1, arg2 ) is not special, it is common.

I was referring the comments such as   " U S E    F U C K I N G    W H I T E S P A C E . "

[ladyattis]

http://en.wikipedia.org/wiki/Indent_style

http://en.wikipedia.org/wiki/Programming_style

Definitely too late for the party, but what the fuck, maybe the stragglers will be able to use these articles from the Mighty Mighty Wiki.

-- Brede

[MobileDigit]

http://en.wikipedia.org/wiki/Indent_style
http://en.wikipedia.org/wiki/Programming_style

Neither of these address the issue of extra spaces after open parens and before closing parens.

[rabidfurby]

#1USEFUCKINGWHITESPACE

Which is easier to read:
#1 USE FUCKING WHITESPACE
or,
# 1  U S E   F U C K I N G   W H I T E S P A C E
?

If you introduce extra spaces it makes it more difficult to scan.

Which is better:
USE FUCKING WHITESPACE
or
USEFUCKINGWHITESPACE
?

Brains work as tokenizers; they break things into chunks based on whitespace. Whitespace should be used to separate things which are logically separate, such as words in prose and arguments to a function call in code. "USE" and "FUCKING" are logically separate, so they should be separately presented. The letters in "USE" and "FUCKING" are part of the same entity, so they should be grouped. Similarly, func(arg1, arg2) makes more sense than func(arg1,arg2) because arg1 and arg2 are two logically separate entities.

However, I think func( arg1, arg2 ) is unnecessary, because the parens themselves act as a delimiter. Same goes for the GNU coding style, which requires a space after the function name - such as "func (arg1, arg2)".

[theCelestrian]

As a former employer who paid people to do this, I'll make this easy:  If you're gonna code for money, and you're part of a development team, your code better follow whatever readability standards your company has set. Period, end of story.

If that means I want you to use white space, tab-indent your code 4 spaces, camelize your variable names, provide pre-conditions and post conditions for your functions and comment explicitly enough so that it actually describes what code is supposed to be doing as well as log any edits that you make to the code...

...then your ass better do it.

If you're coding for youself, who cares?  I don't have to read your code, so do what you want.

[Lindsey]

As a former employer who paid people to do this, I'll make this easy:  If you're gonna code for money, and you're part of a development team, your code better follow whatever readability standards your company has set. Period, end of story.

If that means I want you to use white space, tab-indent your code 4 spaces, camelize your variable names, provide pre-conditions and post conditions for your functions and comment explicitly enough so that it actually describes what code is supposed to be doing as well as log any edits that you make to the code...

...then your ass better do it.

If you're coding for youself, who cares?  I don't have to read your code, so do what you want.

+1

[wtfk]

As a former employer who paid people to do this, I'll make this easy:  If you're gonna code for money, and you're part of a development team, your code better follow whatever readability standards your company has set. Period, end of story.

If that means I want you to use white space, tab-indent your code 4 spaces, camelize your variable names, provide pre-conditions and post conditions for your functions and comment explicitly enough so that it actually describes what code is supposed to be doing as well as log any edits that you make to the code...

...then your ass better do it.

If you're coding for youself, who cares?  I don't have to read your code, so do what you want.

I believe that goes unsaid.  The question had to do with what is preferable.