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 919657
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T18:34:57+00:00 2026-05-15T18:34:57+00:00

I am following some examples in the book, and I noticed two different conventions

  • 0

I am following some examples in the book, and I noticed two different conventions for having various return conditions. Is there any difference between the two?

//example 1
if(someCondition)
{
   return (someValue);
}
return (someOtherValue);

//example 2
if(someCondition)
{
   return (someValue);
}
else
{
   return (someOtherValue);
}

Personally, I like the second example better, because it’s more explicit, and I feel that it’s more readable.

  • 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-15T18:34:57+00:00Added an answer on May 15, 2026 at 6:34 pm

    Avoiding else and taking advantage of early return can keep your code from becoming too deeply nested. Which example looks more readable?

    function doStuff (thing) {
      if (thing.foo) {
        alert ("thing.foo is alive and well");
        if (thing.foo.bar) {
          alert ("thing.foo.bar is alive and well");
          if (thing.foo.bar.baz) {
            alert ("thing.foo.bar.baz is alive and well");
            // TODO: stuff with thing.foo.bar.baz
          } else {
            alert ("thing.foo.bar.baz doesn't exist!");
          }
        } else {
          alert ("thing.foo.bar doesn't exist!");
        }
      } else {
        alert ("thing.foo doesn't exist!");
      }
    }
    

    or

    function doStuff (thing) {
      if (!thing.foo) {
        alert ("thing.foo doesn't exist!");
        return;
      }
      alert ("thing.foo is alive and well");
      if (!thing.foo.bar) {
        alert ("thing.foo.bar doesn't exist!");
        return;
      }
      alert ("thing.foo.bar is alive and well");
      if (!thing.foo.bar.baz) {
        alert ("thing.foo.bar.baz doesn't exist!");
        return;
      }
      alert ("thing.foo.bar.baz is alive and well");
      // TODO: stuff with thing.foo.bar.baz       
    }
    

    … I think the second is much more readable!

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

Sidebar

Related Questions

I noticed for a while now the following syntax in some of our code:
Hi I am quite new to php but i have been following some tutorials
Following is some obviously-defective code for which I think the compiler should emit a
Today at work we came across the following code (some of you might recognize
I have this .NET regex: ^(?<prefix>([^]*))\s(?<attrgroup>(\([^\)]*\)))\s(?<suffix>([^]*))$ It properly matches the following strings: some prefix
Suppose I have the following code: class some_class{}; some_class some_function() { return some_class(); }
I'm considering the following: I have some data stream which I'd like to protect
I'm using the following to grab some updated HTML and insert it into a
What is the reason for the following warning in some C++ compilers? No newline
To do the equivalent of Python list comprehensions, I'm doing the following: some_array.select{|x| x

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.