RE: [Dev-C++] why do we have to rename free() ?

[Khalid El-K. <kha...@ho...>]

> > -----Original Message-----
> > From: dev...@li...
> > [mailto:dev...@li...] On Behalf
> > Of Khalid El-Kary
> > Sent: Thursday, April 03, 2003 5:57 AM
> > To: Dev...@li...
> > Subject: [Dev-C++] why do we have to rename free() ?
> >
> >
> > hi fellows,
> >
> > when i checked a lot of big project's source codes, I have found them
> > replacing basic funtion names with new function names, and
> > sometimes with a
> > new way of functioning for example:
> >
> > free() -> OPENSSL_free()
> > malloc() -> gnew(type, number of blocks)
> >
> > how can this be useful ?, does it have a thing to do with
> > portability ?, and
> > if not what's the difference in functionality ?
>
>
>Additional, non-portable functionality.

I thought GNU, Apache, PHP, OPENSSL try to make there code as portable as 
possible ?

>
>
>
>Ioannis Vranos
>
>* Programming pages: http://www.noicys.freeurl.com
>* Alternative URL: http://run.to/noicys


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail