# Best Practice for Error handing

**URL:** https://swi-prolog.discourse.group/t/best-practice-for-error-handing/4559
**Category:** Discussion
**Created:** [October 14, 2021, 6:00pm UTC](https://swi-prolog.discourse.group/t/best-practice-for-error-handing/4559 "2021-10-14T18:00:12Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![peter.ludemann](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/peter.ludemann/32/48_2.png) [@peter.ludemann](https://swi-prolog.discourse.group/u/peter.ludemann)
#### Post date: [October 14, 2021, 6:15pm UTC](https://swi-prolog.discourse.group/t/best-practice-for-error-handing/4559/2 "2021-10-14T18:15:37Z")

</div>

There’s also a discussion here:

> [@Errors considered harmful](https://swi-prolog.discourse.group/t/errors-considered-harmful/3574):
>
> Interesting discussion on Picat extensions and cuts and I’d like to add my own personal pet peeve with “standard” Prolog. I don’t think there would be much opposition to the topic title. After all (unhandled) errors rip control away from the programmer and terminate the search for solutions. There might be perfectly valid solutions produced by backtracking but they never get to see the light of day. So one of the objectives of debugging a program, in addition to ensuring that successful executi…

---

_[View the full topic](https://swi-prolog.discourse.group/t/best-practice-for-error-handing/4559)._