Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83883
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.49 cause and error)
MIME-Version: 1.0
In-Reply-To: <CA+9eiLsDt9K+DNrnT3Dh7eMwOBCoaP_xgnjNtptu03P8JnmzwQ@mail.gmail.com>
References: <CA+9eiLsDt9K+DNrnT3Dh7eMwOBCoaP_xgnjNtptu03P8JnmzwQ@mail.gmail.com>
Date: Thu, 26 Feb 2015 11:34:13 +0100
Message-ID: <CAEPJdunZpePBb1w6=AEZKxjj_7EZaPLGONkBr40q5=9fOXptpw@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bd6adce0549c8050ffb4b93
Subject: Re: [PHP-DEV] Strict typing and callback vs declare()
From: kontakt@beberlei.de (Benjamin Eberlei)

--047d7bd6adce0549c8050ffb4b93
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 26, 2015 at 11:10 AM, Dmitry Stogov <dmitry@zend.com> wrote:

> Hi Anthony,
>
> What do you think about using a user level callback for strict type checks
> instead of declare(). It won't allow changing behavior per file, but this
> has its own cons and pros.
>
> <?php
> set_strict_type_checker(function ($class_name, $function_nume, $arg_num,
> $expected_type, $value, $file, $line) {
>   ...
>   return false;
> });
> include("orig_index.php");
> ?>
>
> If callback is not set, arguments are converted according to standard
> rules, if set and returns false - fatal error or exception is thrown.
>
> The implementation should be simpler and more efficient than using
> declare().
>
> Thanks. Dmitry.
>

This ruins portability with third party libraries completely.

--047d7bd6adce0549c8050ffb4b93--