this post was submitted on 01 Sep 2024
38 points (100.0% liked)

Learn Programming

1624 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
Ategon
JaumeI
bugsmith
38
Is it better to check if a file exists before trying to load it, or to try to load it, and catch the error and move on? (lemmy.ml)
submitted 2 weeks ago by [email protected] to c/learn_programming
16 comments fedilink hide all child comments
 

For context, I am trying to do a save system for a game.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 2 weeks ago

General wisdom is that if you can perform some kind of pre-validation action to prevent an exception from occurring, you should do that, rather than expect the exception and handle it, as part of "normal" flow control.

However.

Some types of exceptions, especially when related to itneracting with shared/external systems, cannot be conpletely avoided. Checking for the existence of a file is the textbook example of this. No matter how much you check of the existence of the file, it could technically be deleted or exclusively locked by another process before you get a chance to actually open it.

For all intents and purposes, that's not really likely to happen, so by all means, check for the file, to keep your code sensible, but make sure you have a general strategy for exception handling in place as well.