Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34358
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sambarrow.com from 205.234.132.11 cause and error)
To: Stanislav Malyshev <stas@zend.com>
Cc: Jochem Maas <jochem@iamjochem.com>, internals@lists.php.net
In-Reply-To: <477D557F.1030706@zend.com>
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>
	 <477D557F.1030706@zend.com>
Content-Type: text/plain
Date: Thu, 03 Jan 2008 16:44:44 -0500
Message-ID: <1199396684.15292.85.camel@sbarrow-desktop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RE: Optional scalar type hinting
From: sam@sambarrow.com (Sam Barrow)

On Thu, 2008-01-03 at 13:37 -0800, Stanislav Malyshev wrote:
> > 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.

Very true. But we have to make sure to give new features a completely
honest and objective view, strictly on their technical merits.

> > 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.

Definitely, and namespaces have caused me no problems and I've been
developing in PHP 5.3 (heavily using namespaces) for a couple of months.
I supported and still do support the namespace implementation 100%.