Re: valgrind leak I can't find

On Fri, 23 Aug 2024 12:18:38 +0100
Bart <bc@freeuk.com> wrote:

On 23/08/2024 12:03, Stefan Ram wrote:

Mark Summerfield <mark@qtrac.eu> wrote or quoted: 

I don't want to post the code since it is just for me relearning
C. 

 
   It's totally your prerogative if you wanna keep your code
   on the down-low. No need to spill the beans.
 
   But just to cut through the fog in your logic, your "since"
reasoning is a bit of a brain-bender: If I'm cranking out some code
to sharpen my C chops, that's no reason to bury it six feet under
later on.

(I'm creating a tiny collections lib: Vec (of void*), VecStr,
VecInt, SetInt, SetStr.) 

 
   Yeah, for sure. But we got to wonder if these are really
   meat-and-potatoes C problems . . .
 
   Scope out what C was cooked up for in the first place. Eyeball
   those vintage UNIX source files: "find.c", "echo.c", "tar.c",
   "ls.c", "zork.c", "tail.c", and all that noise. How many of
   those kick off with a container library?
 
   What gnarly waves are you missing out on in efficient and
   idiomatic C programming by thinking, "I'll use my container
   library and write C like it's some Silicon Valley startup code!"
 

 
So, what have you done with the real Stefan Ram?
 

It looks like real Stephan Ram hatched out of old restrictive eggshell
few months ago.
BTW, in order to compare his writing style of old with the new one, I
tried to look for his posts on Google Groups. It turned out that I can
only see citations. Posts themselves are not archived. Mysterious.