Code Styling. What do you prefer?

[Kodfod]

So I decided to move from the old topic (post started to get off-topic) and to start off here is the style debated:

[The_Doctors_Life]

I like the one on the left more, even though it doesn’t look neat(Curse u OCD)

[Aaron1011]

There are two types of people. Programmers will know

There’s many names for those two styles, but the one on the left (brackets on their own line) is correctly called the wrong way.

The one on the right (brackets on the same line as the condition) is similarly known as the right way.

[FerusGrim]

It depends on the language’s standard convention.

The left side is completely normal for C++/C, whereas the right side is the normal for Java.

EDIT: And, of course, they’re both perfectly valid to crossover. Just commenting on what’s normally done.

[boformer]

@Aaron1011

There’s many names for those two styles, but the one on the left (brackets on their own line) is correctly called the wrong way.

The one on the right (brackets on the same line as the condition) is similarly known as the right way.

Just found this style on wikipedia:

while (x == y)
{   something();
    somethingelse();
    //...
    if (x < 0)
    {   printf("Negative");
        negative(x);
    }
    else
    {   printf("Non-negative");
        nonnegative(x);
    }
}
finalthing();

[doot]

That disgusts me.

[FerusGrim]

I kind of like that one.

[Kodfod]

How about these two?

//Single line block
if (x == y) return true;

//Multiline block
if (x == y) {
  return true;
}

Personally, I use the first one where possible. It’s less lines and still remains neat looking.

[boformer]

@Kodfod

x = y

How about ==?
Although = should compile if x and y are booleans, right?

I also prefer the short variant, but sometimes I’m using the second to highlight the importance.

I think we should create a new topic for code style discussion

[DarkArcana]

Here’s another style for you guys. A python programmer trying java:

[Kodfod]

@boformer Just moved the off topic posts over to this new topic!

@DarkArcana What is that madness. I can’t even…

[DarkArcana]

The whitespace is allowed. Even newlines are allowed. A statement must terminate with a ‘;’ to be syntactically correct. Blocks must terminate with the ending brace to be syntactically correct. As far as the compiler is concerned, everything there looks correct. It would just be a bit of a nightmare to maintain the semicolons and braces at the end of the line. However, the rest of the syntax follows python’s indentation and format.

[boformer]

Next question: Do you prefer short names (Player p) or lowercase class names (Player player) for internal variables?

I prefer the long names.

[Kodfod]

It depends. If it is self explanatory like:

(Player player)
(CustomType customType) | (Banana banana)

The Banana Class

public class Banana {
   String color;
   boolean peeled;
   int maturity;
void mature (int amount) {

//Modify the maturity

}
void peel () {

//Peel that banana!!!

}
void eat () {

//Eat that lovely banna

}

}

Then I prefer the single letter var names.

(Player p)
(CustomType ct) | (Banana b)

It also depends how many arguments I’m having to work with. If it looks like this:

private void doSomething (String message, int length, String[] players) {}

Then I would not have them looking like:

private void doSomething (String msg, int l, String[] p) {}

---

What about for loops?

When looping an Array which one would you do:
String[] names = {“Kodfod”, “Boformer”, “DarkArcana”, “DotDash”};

for (String name : names) {

System.out.println(name);

}
Or would you do:
String[] names = {“Kodfod”, “Boformer”, “DarkArcana”, “DotDash”};

for (int i = 0; i < names.length(); i++) {

System.out.println(names[i]);

}
Personally I would do the first one. 

[The_Doctors_Life]

If was defined ealier, I would prefer p as it’s easier where as if it isn’t defined I rather have it be player.
Just my two cents (There isn’t a cent emoji? Needs to be added)

[boformer]

Of course the “for each” loop is shorter than the usual “for” loop, but sometimes it is necessary to know the index of the current element (e.g. to identify the first/last).

[mumfrey]

The one on the right (brackets on the same line as the condition) is similarly known as the right way.

Actually it’s now affectionately called Egyptian Brackets (number 3)

By the way, there is a third (horrible) style I’ve seen used:

if (condition)
    {
    // code here indented at the same level as the braces
    }

[TBotV63]

void doStuff(String[] args) or void doStuff(String args[])

I’ve seen both used to solve the same problem… I prefer the first.

[doot]

There’s also String[] args[]

[TBotV63]

ew. <ghjkl,kjhgfdsfghjk>