X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Tue, 20 Aug 2019 17:31:49 +0300 Message-Id: <83d0gzlxgq.fsf@gnu.org> From: "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" To: djgpp AT delorie DOT com In-reply-to: (message from Rod Pemberton on Tue, 20 Aug 2019 05:43:54 -0400) Subject: Re: [PATCH] exec: fix inversions in leak detection logic References: <964e3268-2f75-ee73-ab5a-b01bf1aadb98 AT yandex DOT ru> <7209026e-1f1b-e590-00a3-4ed1a424cc0d AT yandex DOT ru> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Rod Pemberton > Date: Tue, 20 Aug 2019 05:43:54 -0400 > > DOS and Windows are DJGPP's primary target environments. If the > DJGPP code works properly for DOS and Windows consoles, there is no need > to make it compatible with some other environment That is true, but OTOH there's no special need to refuse the change up front. If the change doesn't cause any trouble to the CWSDPMI based setup on DOS, and helps some other environment do something useful, why should we refuse to make simple changes? I see no reason.