Oh I see. So maybe you should just call it safe_malloc() or it'll be too
confusing :)
At 06:28 AM 7/21/2004 +0900, Moriyoshi Koizumi wrote:
On 2004/07/21, at 6:11, Andi Gutmans wrote:
Looks good but why not rename the function to _safe_pemalloc()? (And of
course rename to safe_pemalloc() as you do later on.
Because it's there just for persistent allocation, while pemalloc() can be
used both ways.
Moriyoshi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
