Message-Id:	<199910111717.TAA11904@public.ndh.com>
From:	"Felix Natter" <fnatter AT gmx DOT net>
Organization:	home.felix
To:	Andris Pavenis <pavenis AT lanet DOT lv>
Date:	Mon, 11 Oct 1999 17:17:44 +0200
MIME-Version:	1.0
Subject:	Re: xmalloc and xfree
CC:	djgpp AT delorie DOT com
References:	<wkbta7v2tg DOT fsf AT mail DOT ndh DOT net>
In-reply-to:	<Pine.A41.4.05.9910110951410.100374-100000@ieva01.lanet.lv>
X-mailer:	Pegasus Mail for Win32 (v3.11)
Reply-To:	djgpp AT delorie DOT com

thanks for your help,
but the problem is that the prototypes
for 'xmalloc' and 'xfree' are (were) commented out
in include/stdlib.h.
shouldn't this be fixed with regard to djdev2.03,
or is it already ?

On 11 Oct 99, at 9:58, Andris Pavenis wrote:
> On 10 Oct 1999, Felix Natter wrote:
> 
> > "Kalum Somaratna" <kalum AT myflat DOT com> writes:
> > > Hi Felix,
> > > The header file wich contain's the definition is stdlib.h  as 
> > > documented in the doc's.
> > > 
> > >  #include <stdlib.h>
> > >  void *xmalloc(size_t size);
> > > 
> > > It is strange that you got the messages. I compiled your program and
> > > it linked without any problems and I also didn't get any undefined
> > > reference's.
> > 
> > did you also not get any warnings like "implicit declaration of ..." ?
> > because that's what I got with gcc-2.8.1, and now with gcc-2.95.1 it's
> > getting an error message
> 
> Yes, now -ansi-pedantic is the default for C++ compiler. Current C++
> standard does not permit implicit declarations. Of course You can use
> command line option -fpermissive to get warnings instead of errors for
> some standard violations. But I suggest to fix Your source better.
> 
> Andris
> 
> 


--
Felix Natter

- Raw text -