Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49378
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=MSYml3nFFY0AFdXQWSgnHulZmUvOghY7Tf5EES3ugIseMyaKp1Ro8x2/XC0rrEflVd
         W/lPeDk8Tza+R8cAQFRkrr/FdwqYAGf487Ogha1gG89vlf+bKD77hKzc0NE5/y2XwdYT
         XE4iFU4WFwgcfk/DvKFmSb7KmS8jsr65NWtUU=
MIME-Version: 1.0
In-Reply-To: <7.0.1.0.2.20100811225933.0ef42d88@zend.com>
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>
	<7.0.1.0.2.20100811225933.0ef42d88@zend.com>
Date: Thu, 12 Aug 2010 00:11:21 +0400
Message-ID: <AANLkTikBekVu9n2MtzDaNyomHxGqoV_ABgAT02hTthoe@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] back to 5.4 alpha
From: indeyets@gmail.com (Alexey Zakhlestin)

On Thu, Aug 12, 2010 at 12:01 AM, Zeev Suraski <zeev@zend.com> wrote:
> At 22:50 11/08/2010, Alexey Zakhlestin wrote:
>>
>> On Wed, Aug 11, 2010 at 11:41 PM, Lester Caine <lester@lsces.co.uk> wrot=
e:
>> > Ilia Alshanetsky wrote:
>> >>
>> >> +1, I think that's the most sensible solution for now that would allo=
w
>> >> 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 intege=
r
>> > 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 feat=
ure
> being 'optional' does not take away from any confusion or complexity
> associated with it. =C2=A0It's been a design guideline in PHP from the ge=
t go,
> we're not going to give up on it now.

You misunderstood my comment.

Lester asked if he can still have his APIs without type-hinting and I
told him that he can.
That's all

We're not talking about complexities of understanding

--=20
Alexey Zakhlestin
http://www.milkfarmsoft.com/