Re: on memory usage with the 64bit patch, and interpretation of various numbers
| From: | Pierre Joye | Date: | Fri, 16 May 2014 05:30:15 +0000 |
| Subject: | Re: on memory usage with the 64bit patch, and interpretation of various numbers | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74248@lists.php.net to get a copy of this message | ||
On Fri, May 16, 2014 at 7:25 AM, Ulf Wendel <ulf.wendel@phpdoc.de> wrote:
> Assuming unified behaviour is the #1 goal, the lowest common denominator
> could be used instead of the largest. The latter obviously has
> undesired side effects.
Nice rhetoric but sadly missing some of the key points:
- for class/variables and other language keywords, we can keep what we
have (see my other replies for the reasons)
- we can always limit the maximum size of a storage (hash, zval,
buffer, etc) at the implementation
. we already do that
. it still gives us the benefits of using a clean, safe and
standard implementation (see other replies for a more detailed
explanation about these points)
- the lower common denominator, platforms wild is what we do with this patch
--
Pierre
@pierrejoye | http://www.libgd.org