Path: ...!feeds.phibee-telecom.net!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!not-for-mail
From: ram@zedat.fu-berlin.de (Stefan Ram)
Newsgroups: comp.lang.c
Subject: Re: valgrind leak I can't find
Date: 23 Aug 2024 11:03:32 GMT
Organization: Stefan Ram
Lines: 24
Expires: 1 Jul 2025 11:59:58 GMT
Message-ID: <C-20240823115550@ram.dialup.fu-berlin.de>
References: <j8idnQlHTPZXZFv7nZ2dnZfqn_GdnZ2d@brightview.co.uk> <oKScnQbmXbeW5Fr7nZ2dnZfqn_GdnZ2d@brightview.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: news.uni-berlin.de QP2yQBzGS78S5PN7zHKY0QsIrrel4PNAFmVgWf6F46g2mR
Cancel-Lock: sha1:/+HDXTPKAF4oTTBdeE47vcA1Uxs= sha256:dRBpNKdkeGscmv7fGAc3hdIF+qS4Klf1bbeBJMEf8T8=
X-Copyright: (C) Copyright 2024 Stefan Ram. All rights reserved.
	Distribution through any means other than regular usenet
	channels is forbidden. It is forbidden to publish this
	article in the Web, to change URIs of this article into links,
        and to transfer the body without this notice, but quotations
        of parts in other Usenet posts are allowed.
X-No-Archive: Yes
Archive: no
X-No-Archive-Readme: "X-No-Archive" is set, because this prevents some
	services to mirror the article in the web. But the article may
	be kept on a Usenet archive server with only NNTP access.
X-No-Html: yes
Content-Language: en-US
Bytes: 2526

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!"