Re: Joy of this, Joy of that

On 11/23/24 19:16, Charlie Gibbs wrote:

On 2024-11-23, Pancho <Pancho.Jones@proton.me> wrote:
 

On 11/23/24 07:09, Charlie Gibbs wrote:
>

On 2024-11-22, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
>

On Fri, 22 Nov 2024 18:53:28 GMT, Charlie Gibbs wrote:
>

All my programs contain a routine called quit_cleanup(); it takes a
single argument, which is either an error message or NULL.
It frees all allocated memory, closes any open files, etc.

>
But all that is unnecessary if your program is terminating anyway.
>
In *nix C code, a common convention is
>
      if («call failed»)
        {
          perror(«doing what»);
          exit(«nonzero error code»);
        } /*if*/
>
<https://manpages.debian.org/3/perror.3.en.html>

>
Perhaps, but I'm a belt-and-suspenders guy - I like
to explicitly free everything come hell or high water.

>
I can see that is nice, to understand what you have,
but it sounds like hard work.

 It's not, actually.  Think of it like a mechanic methodically
putting all his tools back where they belong in the box when
he's done, rather than leaving them lying around the shop.
 

It's more like carefully packing up a set of disposable tools into their disposable box, and then throwing the whole lot in the bin.

However there are some resource you do need to explicitly
free/release/close, some database locks for instance.

 Therefore, why go the bother of having to memorize which
resources you have to explicity free, and which ones you
don't?  Get into the habit of freeing them all - you might
avoid tedious debugging sessions when you forget which is which.
 

It's hard for me to remember, because I'm so used to C# IDisposable "using" blocks, Java "try-with-resources", even try/catch/finally, etc. I see even C++ has "Resource Acquisition Is Initialization".
My memory is that in practice you normally want to hold critical (unmanaged) resources open for as short at time as possible, and hence you tend to deal with disposal locally to allocation rather than having long lived stuff that needs to be cleaned on exit. But that is just a gut felling, I can't really remember enough to talk sensibly on the subject. I'm sure there are usecases where this doesn't in apply, but in general I think it does.