Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34354
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <477D557F.1030706@zend.com>
Date: Thu, 03 Jan 2008 13:37:03 -0800
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Jochem Maas <jochem@iamjochem.com>
CC: Sam Barrow <sam@sambarrow.com>, internals@lists.php.net
References: <200801031903.01980.tomi@cumulo.fi>	 <1199380881.15292.11.camel@sbarrow-desktop>	 <20080103172813.GQ7861@mint.phcomp.co.uk> <477D2B40.9010302@fischer.name>	 <477D2CDB.3000005@zend.com>	 <alpine.DEB.0.98.0801032022110.4763@kossu.ez.no>	 <477D452A.9090906@zend.com> <1199392531.15292.64.camel@sbarrow-desktop> <477D4ACF.3030006@zend.com> <477D503E.1040701@iamjochem.com>
In-Reply-To: <477D503E.1040701@iamjochem.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RE: Optional scalar type hinting
From: stas@zend.com (Stanislav Malyshev)

> suitable to enterprise level development. it's merely a case of
> not being able to please everyone all of the time (or of not having your cake

PHP is pretty good with pleasing people (including enterprise 
developers) as it is now, and will get better in 5.3 and 6 - without any 
strict typing. So this argument is not exactly in your favor - burden of 
proof is on new feature proposals, and bigger the feature - bigger the 
burden.

> I also seem to remember (forgive me if Im mistaken) that you we're a
> proponent for the increases in strictness surrounding various things related
> to OO. that feels rather hypocritical at some level.

Like what? You don't expect me to have same opinion to all proposals, do 
you?

> you implied in another post that php should have some kind of structured direction.
> how about a language spec and a formal functionality proprosal/acceptance mechanism?

Yes, I'd be happy to see it happening. No, I don't have time to create 
it. If you do - you know where to find a text editor and docbook build 
system ;)

> (preferably one that didn't allow major changes like the inclusion of namespaces into
> a minor release)

5.3 is a "major" release from a lot of aspects, don't let the numbering 
fool you. It is generally accepted that waiting for PHP 6 to make any 
change would be too long. Unfortunately, we couldn't find a number 
between 5 and 6 for a version number, so we'd have to settle on 5.3.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com