X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Mon, 27 Jul 2015 21:22:27 +0300
From: "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Subject: Re: memalign
In-reply-to: <55B6745B.3060409@iki.fi>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83wpxlxxy4.fsf@gnu.org>
References: <CAA2C=vDrxkegZQ09Z6q16KdVoOg1fgGkkA1naCs79V-NNrYPUQ AT mail DOT gmail DOT com> <CAA2C=vD-VHnmMV80PjNwoCW6VmATELe4H+pTxHqTCqpObj8NfA AT mail DOT gmail DOT com> <83d1zg1ep0 DOT fsf AT gnu DOT org> <55B6745B DOT 3060409 AT iki DOT fi>
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: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
> Date: Mon, 27 Jul 2015 21:11:39 +0300
> 
> I would like to postpone separating nmallign() into a separate file after real release of DJGPP v2.05.

Any particular reason?  Can it cause any breakage that you can
envision and describe?  At first glance, it looks like a simple job to
me.

FWIW, I consider the name-space pollution a serious problem, something
that runs a real risk of breaking legitimate programs.