Date: Mon, 11 Oct 1999 19:03:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DJ Delorie <dj AT Delorie DOT com>
cc: djgpp-workers AT Delorie DOT com
Subject: Re: xmalloc and xfree
In-Reply-To: <199910111505.LAA24879@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.991011190233.436C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 11 Oct 1999, DJ Delorie wrote:

> Note that many programs that use xmalloc/xfree provide their own
> (often incompatible) prototypes.  Hence the commenting-out.

Sure, but that was an okay solution as long as it would compile with the 
default switches.  If it now does NOT compile in C++ programs, it is IMHO 
better to supply a wrong prototype that compiles than prevent them from 
compiling at all.