Re: [VOTE] [RFC] 64 bit platform improvements for string length and integer

Hi! > This is a biased argument, you know it, I know it. The key point is > not about the new maximum size of an array or string but the long due > clean and safe 64bit implementation, following well known good > practice (can be seen in almost all other OSS projects out there) and > standards. I personally am still confused about why clean and safe 64-bit implementation requires 64-bit string lengths. > As of now, phpng has been worked on for the last months, totally > privately. And even if it looks promising it is still not remotely > ready to be actually proposed. However it does not prevent you to use > it to stop other improvements, which have been worked on for months, > publically, with continuous tests, status updates, etc. I am not sure > what is happening here is good for PHP. Nobody is proposing to stop other improvements. What people (including myself) are concerned about is that change to 64-bit strings, due to the increase in memory usage, may negate the very perceivable benefits of the phpng and impact performance, all while not being beneficial for 99% of the users. This is something that can not be fixed by saying "phpng is not production quality yet". It is not, but we have an issue here that does not depend on quality of phpng and we need to find a resolution for it. Maybe if we have types cleaned up and compartmentalized, we could have it working with both options and then make a decision based on later performance tests? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227