Re: Joy of this, Joy of that

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 21:40 this Saturday (GMT):

On Sat, 23 Nov 2024 19:16:04 GMT, Charlie Gibbs wrote:
>

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

On Sat, 23 Nov 2024 07:09:11 GMT, 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.

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

>
That actually slows down program termination.

 
The microsecond or two that is wasted is far less than the debugging
time needed when a shortcut goes wrong.

>
Actually, thinking about it, there are some things -- shared memory
sections come to mind -- that are not automatically freed when a process
terminates. But everything else -- memory, open files, network connections
-- will go away automatically.
>
If you have those persistent things that you want to clean up, your
technique won’t be reliable anyway.

Does it get freed up when the other processes that have it open also
close it, or is it stuck until shutdown?
--
user <candycane> is generated from /dev/urandom