/prog/ - Programming★

>>1327

I read from the first post with this image in the quick reply. Thanks for sparing me the effort of actually posting it.

I use this:

if (condition) {
}
else {
}

>>997

Oh sweet christ that is hideous.

>>1254

Holy fuck sperg harder. And be more wrong while you're at it.

Yeah, it's a code block. But it is defined by the if. Without the if, it's useless. If you use the SHIT style you are intentionally detaching the code block from its purpose, making it both harder to read and easier to make mistakes.

You are a SHITlord.

>>1392

R lets you write conditionals and functions with no braces if they evaluate on one line. I don't use it a lot but it is pretty nice.

>>2543

According to OP that is "GOOD". Honestly that is the most common format that I see. I prefer the "BEST" style myself because it helps group my conditional statements but your style is fine too. It's only the "SHIT" style that makes me want to kick babies.

>>2543

I do that too. Mostly for the reasons >>1010 mentioned.

Is it bad if I do this

if ( 000 ) { 000 //000 = 000
} //if (000) close
if (111) {
111 //111 = 111
} //if (111) close

>>2574

>Without the if, it's useless.

Except for avoiding polluting your scope and marking the start/end of conceptual phases in a function.

In VB.Net it uses the funny brace style as intellisense gets confused otherwise

Dim anonType = New With {
            .Id = 1,
            .Value = 999
        }

How about this?

if
    (condition)
{
    statement;
}
    else
{
    statement;
}

What is this weird blub language? I prefer normal, mainstream languages like Common Lisp.

{if (condition)
    {(statement);}
    else {(statement);}}

if (short) statement;

if (medium_length)
    statement;

if (multiple_statements) {
    statement;
    statement;
}
else
    statement;

(if condition then else)

postfix master race coming through.

>>1075

nah

<predicate> ? <consequent> !  <alternative>;

master-race

also c++ master-race :^)

The "Shit" one is the only one that has consistent spacing and indentation. The first 2 look much worse when nested.

>>2800

javascript masturbace

>>2834

The shit one is also the only style that creates security holes.

>>992 (OP)

<code>

switch(condition) {

case 0:

break;

case 1:

break;

}

</code>

>>1337

pic src? it's so hawt i wanna fuck it D:

Either of these when it fits into 80-ish chars

if (condition) statement;
if (condition) {statement1; statement2}

if (condition) {
        statement;
}

if (condition)
{
    statement;
}

You do this

if
{
    statement;
}

to match the braces up, otherwise finding and matching blocks is harder.

>>992 (OP)

These ratings are in reverse.

if(wat && areYouGuysFuckingSerious){
    thisIsTheOnlyAcceptableAlternative();
}else{
    dieInAFire();
}

picked at random from GNU coreutils

http://git.savannah.gnu.org/cgit/coreutils.git/tree/src/whoami.c

void
usage (int status)
{
  if (status != EXIT_SUCCESS)
    emit_try_help ();
  else
    {
      printf (_("Usage: %s [OPTION]...\n"), program_name);
      fputs (_("\
Print the user name associated with the current effective user ID.\n\
Same as id -un.\n\
\n\
"), stdout);
      fputs (HELP_OPTION_DESCRIPTION, stdout);
      fputs (VERSION_OPTION_DESCRIPTION, stdout);
      emit_ancillary_info (PROGRAM_NAME);
    }
  exit (status);
}

if (year >= 2015 && !half_indented_braces)
  {
    shig(dig);
  }

Given we're talking about readability of code, the best way is the easiest way to read code, which means brackets need to be in line with each other.

If you have to spend any time looking or searching for another bracket, its bad. Should be a straight up its directly above or below.

Also fuck using any editor that doesn't highlight the opposing bracket.

>>2997

There's an emacs plugin to fix that

>>3002

if 
(
    bracketsInLine
)
{
 print(
"
holy fuck you're retarded
"
);
}

>>2913

How does it create security holes? It's more readable and the compiler can't tell the difference anyways.