Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29606
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.248 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=jEItXmlKYMK4aOHdgj/RdUaA3YC4sVZFVuAuZ04OFRWUTQ5Gutisrjv8Eo9DvDFFd8xw011TYGY+eVsys5gOS8Vt/89qg4CUUZ3Va1C3dSplmrt+pIhrzGyJgXayv4aS6aVnUiXLdg7wpuGojul+Kpq6ArlzsmDEfstGKzcgXYY=
Message-ID: <cd5680a20705210047q73c71ebbu2372604a8d2c4226@mail.gmail.com>
Date: Mon, 21 May 2007 11:47:33 +0400
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "Stefan Esser" <sesser@hardened-php.net>, David <planetbeing@gmail.com>, 
	internals@lists.php.net
In-Reply-To: <465149FE.4070100@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <465022BE.1020905@hardened-php.net>
	 <7d5a202f0705201415s71982fd2jb61b8bffbb7ba6de@mail.gmail.com>
	 <46513546.5000303@zend.com>
	 <7d5a202f0705202303s2ff4d0cdg1157c1e245c3c2e4@mail.gmail.com>
	 <46513745.7030701@zend.com> <000001c79b71$543e0970$fcba1c50$@com>
	 <46513E93.5000902@hardened-php.net> <465140BE.8050502@zend.com>
	 <4651454B.4080000@hardened-php.net> <465149FE.4070100@zend.com>
Subject: Re: [PHP-DEV] Dismantling the lies...
From: indeyets@gmail.com ("Alexey Zakhlestin")

the problem is, that, in this case, code is not broken. it is not an
error to use large stack.
it is an error to let someone use the low-level side-effects of a
problem in a high-level language.

On 5/21/07, Stanislav Malyshev <stas@zend.com> wrote:
> > Well yes. I think to solve this "once and for all" a public statement by
> > the PHP group would be nice that says:
>
> I don't think they are "not important", just that they are not important
> enough to want them fixed no matter the cost. Running shared hosted
> server in a mode that relies on restricted code IMO is wrong anyway, and
> for non-shared environment these problems could be exploited only if
> specifically enabled by very badly written code. So when there's a
> trade-off between having the language work better for 100% of cases or
> protect those who run broken code on their servers - the choice would be
> to make language run better. Again, that doesn't mean bugs shouldn't be
> fixed - just the fix shouldn't make the situation worse.
> --
> Stanislav Malyshev, Zend Products Engineer
> stas@zend.com  http://www.zend.com/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
Alexey Zakhlestin
http://blog.milkfarmsoft.com/