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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T01:19:06+00:00 2026-06-08T01:19:06+00:00

I see in some of the code on Github if($something_funky_happens){ throw new \LogicException(…); return;

  • 0

I see in some of the code on Github

if($something_funky_happens){
  throw new \LogicException(...);
  return;
}

Is this required, or it is not important to return?
because I know that after you throw exceptions the script stops, so further code does not run

  • 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-06-08T01:19:07+00:00Added an answer on June 8, 2026 at 1:19 am

    unreachable code

    I tend to denote it an error in their code. The statement is not reachable. Every static code anaylsis tool will complain about this unreachable statement. Even when it has no harm in this case you will get a load of warnings when checking your code. If you turn these warning type off you will perhaps miss other logic errors within your code. It’s a real bad smell and it needs to be fixed.

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

Sidebar

Related Questions

In documentation code I see some things like this: /* * @(#)File.java 1.142 09/04/01
So I'm looking through some code, and I see this: class whatever { public:
i see some code like this SERIAL_NO=121 if [ -z ${SERIAL_NO} ]; then echo
I see some code exp_send -i $bash_id /bin/tcsh , what does the -i flag
I see some code where the author has truncated a temp table immediately before
I have some code that is using SyncEnumerator. As you can see here ,
I have an example of some code that I see often in websites that
I've got a list of names which some code checks against to see if
Looking at some assembly code for x86_64 on my Mac, I see the following
I'm reading some ruby code, and see 0..size and 0...size are used in similar

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.