Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37088
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.174 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=L7C+SjKQ2k5iIS9Lell+LoNIXmpaaaMSMZNaKB5B1xo90ymK/Xn5XY6YjPZZS8tuPvqMXdkBJNCgMqlUVxOHpomW0ivzfpEt/kSUa7qSQNXmBvzwRJoie8SQDwKsL0I2vHJK8UTNk4QkLxNykyKDPFC/z/+tG2NEc0pEEtv1XPc=
Message-ID: <e2e02fe0804171006i5efaaeb5lf67752bd3c365305@mail.gmail.com>
Date: Thu, 17 Apr 2008 10:06:17 -0700
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "Felipe Pena" <felipensp@gmail.com>, internals@lists.php.net
In-Reply-To: <48078168.1070801@zend.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_921_12622686.1208451977405"
References: <46ccd1ab0804170742g142ed562t4f03339da549a820@mail.gmail.com>
	 <48077BD2.2000107@zend.com>
	 <e2e02fe0804170950udd38ab3m21e6d658254f042a@mail.gmail.com>
	 <48078168.1070801@zend.com>
Subject: Re: [PHP-DEV] [RFC] Strict type hints (parameter and return value)
From: chrisstocktonaz@gmail.com ("Chris Stockton")

------=_Part_921_12622686.1208451977405
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Thu, Apr 17, 2008 at 9:57 AM, Stanislav Malyshev <stas@zend.com> wrote:

> What's the use of such code? If $var is '1' and not 1, what's the use of
> throwing an exception and having to handle it later (basically by failing
> the task, since you don't know how to do foo() now) - instead of just doing
> with that 1 what was intended for? There's no any difference between 1 and
> '1' that can be important to anybody. Only difference is the way it is
> represented in underlying bits in zvals, about which nobody should ever
> care. That's like making function that would accept only arguments that has
> 3'rd bit of pointer set to 1 and 5th bit set to 0, and reject all others. No
> sane application should ever behave this way. Writing such function is just
> plain wrong, it replaces the substance of programming with nitpicking over
> the details that are not important. Whole phenomenon of dynamic languages
> has grown on the principle of liberating people from caring for bits and
> concentrate on substance, and now you try to drag the bits back in.
> So every time you call foo you need try/catch? And that's supposed to be
> _good_?


Somebody missed the point...

Seeing how you work for zend I thought maybe you have used the zend
framework = ) Sorry in my example I used "int" instead of "numeric", but my
point is the same, grep in zend framework for is_bool.

It does what you are complaining about:

From: Zend_Pdf_Element_Numeric
    public function __construct($val)
    {
        if ( !is_numeric($val) ) {
            throw new Zend_Pdf_Exception('Argument must be numeric');
        }

        $this->value   = $val;
    }

That could be...
    public function __construct(numeric $val)
    {
        $this->value   = $val;
    }

So, let's re-visit my point of "less code bloat"....

------=_Part_921_12622686.1208451977405--