X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Sun, 01 Sep 2019 19:42:17 +0300 Message-Id: <838sr87yty.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: (djgpp AT delorie DOT com) Subject: Re: cwsdpmi borland compatible? possible! (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: "stsp (stsp2 AT yandex DOT ru) [via djgpp AT delorie DOT com]" > Date: Sun, 1 Sep 2019 19:07:49 +0300 > > Now the question is: does anyone here think it would > be a good idea to make cwsdpmi borland-compatible? > (and MS-compatible, and whatever else) Are there any downsides? Also, how large would the changes be?