Looks good!
Andi
At 09:47 AM 10/9/2002 -0400, Jon Parise wrote:
>A new CODING_STANDARDS patch is attached, based on feedback from Andi
>and Dan (thanks!). Please review and comment.
>
>--
>Jon Parise ([EMAIL PROTECTED]) :: The PHP Project (http://www.php.net/)
--
PHP Development Mailing List
Le Mercredi 9 Octobre 2002 16:01, Markus Fischer a écrit :
> On Wed, Oct 09, 2002 at 09:47:10AM -0400, Jon Parise wrote :
> > +[11] Prefer emalloc(), efree(), estrdup(), etc. to their standard C
> > library + counterparts. These functions implement an internal
> > "safety-net" + mechanism
On Wed, Oct 09, 2002 at 09:47:10AM -0400, Jon Parise wrote :
> +[11] Prefer emalloc(), efree(), estrdup(), etc. to their standard C library
> + counterparts. These functions implement an internal "safety-net"
> + mechanism that ensures the deallocation of any unfreed memory at the
> +
A new CODING_STANDARDS patch is attached, based on feedback from Andi
and Dan (thanks!). Please review and comment.
--
Jon Parise ([EMAIL PROTECTED]) :: The PHP Project (http://www.php.net/)
Index: CODING_STANDARDS
===
RCS file:
It might be a good idea to mention that almost in all cases memory returned
to the engine has to be emalloced.
You can also mention that malloc() also should be used if the memory has to
survive in between requests.
Andi
At 10:14 PM 10/8/2002 -0400, Jon Parise wrote:
>Attached is a patch that
Attached is a patch that adds a new item to CODING_STANDARDS that
suggests using emalloc() and friends over the standard C library
version. It also offers an explanation, courtesy of Rasmus' reply to
my earlier question on the subject.
If no one objects to the addition in principle or in wording
