Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74248
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5375A15A.5020104@phpdoc.de>
References: <CAEZPtU6OfLM7M31TeoO587aeVgskEy9ZrUaMv-t7sq0g2spSdw@mail.gmail.com>
	<537539AC.8080906@sugarcrm.com>
	<CAEZPtU6sTGh_XWJedQs4KCuzUxDsuhnLwkgLJj3tGdPvRG3Tng@mail.gmail.com>
	<5375A15A.5020104@phpdoc.de>
Date: Fri, 16 May 2014 07:30:15 +0200
Message-ID: <CAEZPtU7wvFVCjrCSr=JJ7hOm8bHJ7N7M4OPnoNke91L+NqN3cQ@mail.gmail.com>
To: Ulf Wendel <ulf.wendel@phpdoc.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] on memory usage with the 64bit patch, and
 interpretation of various numbers
From: pierre.php@gmail.com (Pierre Joye)

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