MB>>size_t is a specialized typedef for the exact purpose, being capable of MB>>handling any size a pointer can store.
Right. MB>>for you then most probably we have thousands of potential 64bit memory MB>>corruption issues. Or sizeof(zend_uint) is bigger then sizeof(size_t) MB>>which is then only a waste of time. Yes, it is. So you can not use address of size_t instead as zend_uint *, because when you assign uint *, part of size_t remains unassigned. This is the source of the bug. MB>>Typically *uint is translated to unsigned int which is on 64 bit typically MB>>64 bit. On 32 bit both are 32 bit. Fine so far. However there are systems On which exactly 64-bit platforms unisgned int is 64-bit? MB>>where size_t is bigger then unsigned int. This happens for example when you MB>>have a 32 bit intel with PAE support. This happens also on sparc64 and amd64. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
