Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49377
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.185 as permitted sender)
Message-ID: <7.0.1.0.2.20100811225933.0ef42d88@zend.com>
Date: Wed, 11 Aug 2010 23:01:05 +0300
To: Alexey Zakhlestin <indeyets@gmail.com>
Cc: Lester Caine <lester@lsces.co.uk>,
 PHP internals <internals@lists.php.net>
In-Reply-To: <AANLkTikuWfufFYiRmS=-f1_P43rS4=x=TQZ8kzNM+Skf@mail.gmail.c
 om>
References: <4C62EC4A.9020106@sugarcrm.com>
 <AANLkTi=83BdZOkCoAMY=BpiS6SRXodWEz7SaB6Mhgy38@mail.gmail.com>
 <4C62FD01.7010306@lsces.co.uk>
 <AANLkTikuWfufFYiRmS=-f1_P43rS4=x=TQZ8kzNM+Skf@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] back to 5.4 alpha
From: zeev@zend.com (Zeev Suraski)

At 22:50 11/08/2010, Alexey Zakhlestin wrote:
>On Wed, Aug 11, 2010 at 11:41 PM, Lester Caine <lester@lsces.co.uk> wrote:
> > Ilia Alshanetsky wrote:
> >>
> >> +1, I think that's the most sensible solution for now that would allow
> >> us to proceed with 5.4, something we all seem to be in agreement on.
> >
> > A slight aside here, as I have not be bothering about what HAS been
> > implemented typing wise ... A large section of the code a work 
> with passes a
> > range of data to functions and classes. If the function gets an integer it
> > looks up the record with that id, an array assumes the data is already
> > loaded, and perhaps a string value defines that a new record of 
> that name is
> > to be created. So I don't want the parameters passed to be tied to a single
> > type. Is THAT affected by any of the current typing actions?
>
>both suggested type-hinting strategies are optional.
>so, you, as developer, are free to not use type-hinting and accept any
>data you like

Alexey,

It's been explained countless times why this is WRONG.
Please read the archives.
If you have and you disagree with it, please take it as an axiom - a 
feature being 'optional' does not take away from any confusion or 
complexity associated with it.  It's been a design guideline in PHP 
from the get go, we're not going to give up on it now.

Zeev