Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1078043
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T21:40:01+00:00 2026-05-16T21:40:01+00:00

I always write if statements like this: if (…) { /* do something */

  • 0

I always write if statements like this:

if (...) {
    /* do something */
}

When I create topics on stackoverflow, sometimes people change this code to:

if (...)
{
    /* do something */
}

So the first { goes to a new line.

Does it make sense, what’s the true way?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T21:40:02+00:00Added an answer on May 16, 2026 at 9:40 pm

    I’d suggest reading Code Complete. He goes into quite depth on the subject (Devoting practically an entire chapter on it), and gives what I see as a convincing argument for #1.

    He actually says not to use the second one explicitly since it fails the black box test:

    if (blah) 
    {
        //Foo
    }
    

    When black boxed turns into:

    XXXXXXXXX
    X
        XXX
    X
    

    So the opening brace is seeming like the start of the block, wheras it’s not (it’s just the delimiter).

    Instead, he recommends either the first option (opening brace on the same line), or:

    if (blah)
        {
        //Foo
    }
    

    Since it passes the black box test:

    XXXXXXXXXX
        X
        XXXXXXX
    X
    

    Note: I can’t remember if the closing delimiter is supposed to be inside the block or not… I don’t have my copy handy, so it might be:

    if (blah) 
        {
        //Foo
        }
    

    However, it all boils down to consistency. In order for your code to be readable, you need to be consistent in how you format it. Pick a method, and then stick to it. Don’t switch from file to file or routine to routine. So long as you’re consistent and actually format it, don’t worry about it…

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a code that does something like this: while (doorIsLocked()) { knockOnDoor(); }
When I code, I always write little pieces of unit, and compile it often.
It always feels wrong to me to write if (MyObject) // do something Or
Suppose I write my code very defensively and always check the return types from
Why does everyone tell me writing code like this is a bad practice? if
I have a table that simplified looks like this: create table Test ( ValidFrom
I am using the following code to create a file, but it always failed
Currently I am using something like this for ARC compatibility between iOS 4.0~4.3: -
We always write functions or classes and their logic is very complicated. If there
I can always start to write my own, but i'd rather not have to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.