Re: encapsulating directory operations

On 6/8/2025 9:58 AM, Scott Lurndal wrote:

Bonita Montero <Bonita.Montero@gmail.com> writes:

Am 07.06.2025 um 23:12 schrieb Janis Papanagnou:
>

Context, in the general case, matters. ...

>
If you need the context then you catch the exception near where
it is thrown; but that's not usual, meaning in most cases you
don't need that context. F.e. when a bad_alloc is thown it dosn't
matter which allocation failed, it's just enough to know that a
memory-collapse happened.

 Actually it very much matters where the allocation failed, if
one wishes to recover from it. 

Exactly. If an allocation failed in some of my older server code, 20 years ago for sure. Well, it would make the server go into a sort of "panic mode" and dump cache, dump timed out connections, ect, then it would try the allocation again. If that failed, it would go into shit hit the fan mode... ;^)
Another fun aspect is in panic mode, instead of dumping timedout connections that are deemed worthy, I send them a special packet. It says, disconnect from me and connect to my friend server, here is the address and port.

It seems your concept of error
handling is simply reporting it (hopefully with sufficient
context information for the user to understand what needs to
be fixed) and calling exit().