Thread: Programming Style? Which is preferred??

Hey guys, I am pretty new here and although I have learnt programming for some time now, I am still "raw"

Anyway, just like to know what format do you (or any other real professional programmers) prefer:

1)

int main () {
//body
}

OR

2)

int main ()
{
//body
}

Personally I prefer 1) cause it makes the code easier to read, but.......

its all personal preference use what you like best.

but since you asked i use 2.

Its really funny, when I started programming, I used 2) too, but since I started college, everyone i know uses 1).....before long, I too am using 1)

2 - always.

I use 2 as well. It seems easier to read that way.

Actually, I prefer a variation of 1. Functions and structures use an Allman style for the braces while loops and control structures use a K&R style.

Code:

int main ( void )
{
  int i = 0;
  if ( i == 0 ) {
    puts ( "Fooby" );
  }
  return EXIT_SUCCESS;
}

Lining up the braces doesn't matter if the code was indented properly, and I've found that I can read code more easily that uses this style with an indention of 2 spaces. But code formatting is very much the preference of the programmer.

-Prelude

I use no. 2
int main ()
{
.........
........
}

Whoah, so I guess 2) really is more popular!

Prelude's style is really a great idea, I guess I will adopt that

Come to think of it, I guess what I started using 1) is because one of my instructors suggested a general rule is that anything more than a page of code should be broken down into different functions...

So if I use 1) I would run out of space pretty soon! Well, in the end, I started using 1) but my code still ends up longer than a page for each function!

>but my code still ends up longer than a page for each function!
It depends on the complexity of the function. If your function does something simple and is very long then you might want to consider redesigning it into several functions. A good rule of thumb is to modularize functions in such a way as to have each function perform one operation, like an assembly line. Each person on an assembly line performs one operation and does it well, but when put together, all of the people make something big.

The style of your code doesn't matter as long as someone can pick it up and read it without having to ask you what something does or where you have so and so. Compact is good to a point, but some people take it to the extreme, my functions tend to be rather short but they are still easy to follow for anyone with a grasp of the basic syntax of the language.

-Prelude