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

  • Home
  • SEARCH
  • 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 986225
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T05:17:13+00:00 2026-05-16T05:17:13+00:00

Possible Duplicate: What is the advantage of using try {} catch {} versus if

  • 0

Possible Duplicate:
What is the advantage of using try {} catch {} versus if {} else {}

I’d like to know whether, generally speaking, it’s better to use a try/catch construct or to try to prevent this exception by (excessive?) use of if/else. Example: should I catch a FileNotFoundException, or should I test and try to find the file first.

What would be the best approach?

  • 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-16T05:17:14+00:00Added an answer on May 16, 2026 at 5:17 am

    They are totally different. They are not interchangeable, and which is appropriate is determined by the requirement and context.

    EDIT: This answer is based on the original, unedited question. The original, in it’s entirety was:

    PHP : if/else vs try/catch

    which is better

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

Sidebar

Related Questions

Possible Duplicate: Why use getters and setters? Is there any advantage to making methods
Possible Duplicate: C++ char* vs std::string Is there any advantage to using char*'s instead
Possible Duplicate: In Java, what is the advantage of using BufferedWriter to append to
Possible Duplicate: sorted() using Generator Expressions Rather Than Lists We all know using generators
Possible Duplicate: Biggest advantage to using ASP.Net MVC vs web forms I was reading
Possible Duplicate: Biggest advantage to using ASP.Net MVC vs web forms maybe it feels
Possible Duplicate: Biggest advantage to using ASP.Net MVC vs web forms I'm soon gonna
Possible Duplicate: Using an ORM or plain SQL? Would you elect to use an
Possible Duplicate: C#: Public Fields versus Automatic Properties Do I need to use {
Possible Duplicate: How do I make a request using HTTP basic authentication with PHP

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.