From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: scratch/igc: Avoid MPS being interrupted by signals Date: Wed, 08 Jan 2025 17:42:51 +0200 Message-ID: <86sept2txg.fsf@gnu.org> References: <87ldvlg17a.fsf@protonmail.com> <86zfk1306e.fsf@gnu.org> <86v7up2xus.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6655"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pipcet@protonmail.com, emacs-devel@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 08 16:44:11 2025 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tVYE7-0001bm-3e for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Jan 2025 16:44:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tVYDE-0006Rj-Gj; Wed, 08 Jan 2025 10:43:16 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tVYDC-0006Ra-T5 for emacs-devel@gnu.org; Wed, 08 Jan 2025 10:43:15 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tVYDC-0003Kl-KT; Wed, 08 Jan 2025 10:43:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=a9E+1kRUti0+jkrFNxfpg8n/SSWlV2mXm/MG5oruUqU=; b=pXaJ4rkDowPge8tYKC1e YDBfizJ1E5BAkeGyyTz9cGQw+xUVoVrlgfc9LwHUkkRrbljrZ/ZhmL4h5EsulbU28XhY09/37q1B2 3SKEMob80mpT1UY6mK4RInsEYL8JGKSlzNHV2EvA76cqrLFnwuKPrtG+IGz2DlkPEpGDeH5B5DOJm lhM7a/VlLCKnqbwrTt5R90BATAWPUCRGjWn+HC4zhp2y4Zc8lLQdR/N1fma5D1NtOFnVYIVguM2cO P3gizeWOPbyeO8yGrA83phqcPA1ksABp6XhQPuixLC8QUqT0iuesa3efntiaM+XumfIwWew1y1a8F +jII2iWLV+yoKw==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Wed, 08 Jan 2025 15:46:05 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327795 Archived-At: > From: Gerd Möllmann > Cc: pipcet@protonmail.com, emacs-devel@gnu.org > Date: Wed, 08 Jan 2025 15:46:05 +0100 > > Eli Zaretskii writes: > > >> What about your request to discuss changes on the branch before > >> committing? Is that off the table? > > > > I asked that about the patch which xstrdup's strings before putting > > them into SAFE_NALLOCA'd array in callproc.c. That was discussed > > enough, and now is installed, so that issue is closed, from where I > > stand. > > > > I also asked to discuss each place where you suggest replacing > > SAFE_ALLOCA and its ilk -- is that what you are asking about? > > Yes, these. Long draining threads with indefinite outcome, from my POV, What can I do to make them shorter and more to the point? I think these discussions are important to establish the safe coding rules when using MPS. > It's good to hear now that you got something out of this you wanted to > know. But I would have found it nice if you would let me know. Others > too of course. Sorry. > Or we let things just happen, discuss only if there are concrete > questions, or whatever. I don't know either. Main thing for me is to > avoid endless palaver where everyone is a bit dumber and drained in the > end. Me too.