From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 13992 invoked from network); 6 Feb 2022 00:56:41 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 6 Feb 2022 00:56:41 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 934659BC14; Sun, 6 Feb 2022 10:56:36 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 424909B7AF; Sun, 6 Feb 2022 10:56:14 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 53D3C9B7AF; Sun, 6 Feb 2022 10:56:10 +1000 (AEST) Received: from mcvoy.com (mcvoy.com [192.169.23.250]) by minnie.tuhs.org (Postfix) with ESMTPS id DD8F19B68F for ; Sun, 6 Feb 2022 10:56:09 +1000 (AEST) Received: by mcvoy.com (Postfix, from userid 3546) id 7323635E1B7; Sat, 5 Feb 2022 16:56:09 -0800 (PST) Date: Sat, 5 Feb 2022 16:56:09 -0800 From: Larry McVoy To: Hellwig Geisse Message-ID: <20220206005609.GG3045@mcvoy.com> References: <20220201155225.5A9541FB21@orac.inputplus.co.uk> <202202020747.2127lTTh005669@freefriends.org> <7C19F93B-4F21-4BB1-A064-0307D3568DB7@cfcl.com> <1nFWmo-1Gn-00@marmaro.de> <1644006490.2458.78.camel@mni.thm.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1644006490.2458.78.camel@mni.thm.de> User-Agent: Mutt/1.5.24 (2015-08-30) Subject: Re: [TUHS] more about Brian... X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: tuhs@minnie.tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On Fri, Feb 04, 2022 at 09:28:10PM +0100, Hellwig Geisse wrote: > Hi Thomas, > > On Fr, 2022-02-04 at 20:45 +0100, Thomas Paulsen wrote: > > I tell you one thing: I never ever experienced any problems with > > traditional malloc()/free().?? > > did you ever write a program which does heavy malloc()/free() > on complicated (i.e., shared) data structures *and* runs for > days, perhaps weeks? IMO it's very difficult to do this without > a GC, and you have to exercise quite an amount of discipline > to do it right. I've done this and I've employed people who have done this. We're a dieing breed, the focus seems to be on programming languages and tools for idiots. People don't want to learn the discipline it takes to work with malloc()/free(). It's sad.