Closed notoria closed 1 year ago
It is a deliberate deviation from the standard. SWI-Prolog searches for a matching catch/3
before unwinding the exception and backtracking. The advantage of that is that we have all context around when deciding the exception is uncaught and therefore can trap the debugger will all relevant information for debugging still around.
Expected the same result as the first query.