Perhaps it'd be a nice alternative to have an optional parameter? Having 4 functions for checking memory usage is quite a lot, isn't it?
I would humbly prefer seeing: int memory_get_usage([bool realusage]) int memory_get_peak_usage([bool realusage]) - Ron "Derick Rethans" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > On Tue, 25 Jul 2006, Dmitry Stogov wrote: > >> > > Right now memory_get[peak_]usage() show the amount of REAL memory >> > > that PHP (Zend Memory Manager) takes from system. >> > > >> > > Previous memory manager showed size of emalloc()-ed memory without >> > > malloc() overhead. Also it didn't consider internal caches. >> > > >> > > We need decide which behavior to use before 5.2.0 release. >> > >> > I would definitely want a more precise memory usage. >> >> We can revert "allocated_memory" semantic. >> This is not a problem. >> >> > However, we can add the new one as a different function (or atleast >> > some internal value in AG). >> > >> > For now, this change breaks some BC with extensions (like Xdebug) >> > that use AG(allocated_memory). >> >> Please use new API functions to access them. > > What are the new functions? > > Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
