What is the best way to use whitespace while progr

问题:

I'm fairly new to programming and from learning I have seen different ways of formatting code, comments, etc; and have been recommended on different techniques.

I mostly program in C#, C++, and Java so I want to know what is the the best way to layout code so that if other people where to go through it, they would be impressed by how simple and easy to understand it is.

回答1:

The best rule to follow is: (and probably the only rule everyone will agree on)

Be consistent!

Pick one style and stick with it. Always put your braces in the same place. Use similar naming conventions. Don't mix tabs and spaces, etc...

That being said. It is also usually a good idea to try and follow the conventions already in place for a language.

When working on a team with people, make sure that you all agree upon a style and stick with it. If you don't, often times one developer will reformat a file with their auto-formatter, and then you can have hundreds of little conflicts that were just caused by whitespace.

回答2:

Keep your diffs clean.

Do whatever you like with whitespace under the following restrictions:

1. Don't commit changes in whitespace together with changes in code
2. Don't change whitespace in an existing file unless you have a good (reasonably objective) argument for it.

Why?

The most important factor in dealing with whitespace is not readability of the files themselves, but the readability of the diffs. The diffs are the things that you'll be looking at when cold sweat is trickling down your spine and thinking seems harder than usual.

The above two rules make sure the diffs are clean and readable. Being consistent in how you deal with whitespace helps, but it is foolproof only in a perfect world. It is a nice thing to strive for, but not as important as keeping the diffs clean.

As an optimization you can try to agree on code style with others so you don't waste time complying with 1 and 2.

回答3:

Thing almost everyone will agree on:

• Put spaces after commas
• Put newlines after semicolons (with the exception of for loop declarations)
• Indent the body of all blocks (anything inside {}) by one tab or four spaces (your choice)
• Put a newline after a closing } that ends a block (with a few exceptions)

There are a lot more things than that which some teams will insist upon for consistency, but these elements of code formatting are universal.

There are basically two ways to deal with if blocks and anything with the same format (for, while, using, etc):

if (condition) {
    /* code */
}

versus:

if (condition)
{
    /* code */
}

This is purely a matter of preference. Pick one style and stick with it (or conform to the rest of your team).

One possible exception to the "newline after }" rule is for grouped if/else if/else, blocks, try/catch blocks, or other closely-connected blocks, which many people prefer to space thusly:

if (condition) {
    /* code */
} else if (condition2) {
    /* code */
} else {
    /* code */
}

回答4:

Be consistent, even when modifying another developers code. If the indenting standards (if any) of your project don't prescribe how to format your code, or your don't use an automatic tool like Narrange, or Resharper, then try to stick with the formatting used by the other developer. Yes, do turn on white space indicators if you have to (for the tab vs. spaces debate)

回答5:

This is a pretty controversial (and subjective) topic, so there's not going to be a "correct" answer. However, my advice is use vertical whitespace sparingly, as too much of it reduces the amount of code one can see on-screen at a given time.

I personally like to use horizontal whitespace to make code more readable like so:

public void MyMethod( int param1, double param2 ) {
    if ( param1 < param 2 ) {
        member.OtherMethod( param1 );
    }
}

...but really, to each his/her own. :)

Also, if you're using Visual Studio or another tool that supports it, spend the time to set up your auto-formatting rules, and use the auto-format religiously. :) It will really help to keep your code clean and consistent.

回答6:

The most important things are that

1. Readable to you
2. Readable to others working on the project

Everyone will have their own nuances. If your boss says you -must- use tabs, then you use tabs. If the company convention is 4 spaces on compiled code and 2 on meta data files, that's what you do.

But be consistent, and make sure it's readable. Readability is the only significant criteria.

回答7:

The whitespace programming language. A language that only has white spaces

回答8:

Whitespace is not the primary factor in creating readable code. Indeed, I would never be "impressed by how simple and easy to understand it is" due to the author's use of white space. I might go the other way and think that some code is very unreadable due to a poor use of whitespace, but at best you're going to get me to not be disappointed in you.

Real readability comes from modularized, self documenting code. It flows out of consistency, intelligent naming of fields and functions, and design principles (especially separating concerns). These things will impress me. For whitespace, I have auto-formatters.

As for suggestions on best practices with whitespace, I think the other answers have all the good points covered.

回答9:

I recommend you read Code Complete and Clean Code. These books will teach you about formatting code, commenting, and many more topics.

回答10:

Some stuff to do: Be sure to search Stack Overflow for more examples with similar tags.

What does a good programmer's code look like?

https://stackoverflow.com/questions/563036/what-is-elegant-code

Stuff NOT to do:

https://stackoverflow.com/questions/237719/most-frustrating-programming-style-youve-encountered

回答11:

There is no "best" formatting, but if you use the same formatting as most other programmers, its easier for them to read your code, and it becomes easier for you to read their code!

Some guidelines to find out how other programmers use white sapces (from the java world):

• read a "style guide" (like the Elements of Java style
• read well-known code examples (for examples, the JDK contains the source code for all non-native JRE classes)
• look at what your tools support (Eclipse has an "auto format" function, Ctrl+Shift+F); just let the tool indent your code!

回答12:

There are many styles or coding rules around. I think nobody will be impressed by layout or spacing and pay more attention to the code itself. Tools can convert from one coding style to another (code beautifier) so that you can pretty safely choose any style. Like jjnguy said, most important is to be consistent.

回答13:

In general, whitespace is your friend. Add it whereever it makes code more readable. Whitespace compiles to the most efficient code possible: none!

In general, and this is subjective...

Open and close curly braces (e.g., { and }) go on a line by themselves. (Exception for javascript, where open curly brace goes on the line that creates the block.)

Leave a blank line between methods.

If it helps readability, leave a blank line between properties.

It's not strictly a whitespace issue, but only declare one variable per line. Don't stack variables in declarations.

int i, j;  // stacked declaration - don't do this!

Don't stack multiple statements on one line, either.

Keep your indentations easily readable; usually 4 spaces is good.

Keep line lengths short enough to fit on your monitor. Split long lines of code, and indent continuations.

If a parameter list is too long for a single line, format with one parameter per line.

That should get you started.