Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86281
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.213.46 cause and error)
MIME-Version: 1.0
In-Reply-To: <CABBJUpc3MzKM35CKXUAeUL3oiAqdFXXAyeW4-wChTZH1V9tumw@mail.gmail.com>
References: <CABBJUpc3MzKM35CKXUAeUL3oiAqdFXXAyeW4-wChTZH1V9tumw@mail.gmail.com>
Date: Sun, 17 May 2015 00:20:13 +0000
Message-ID: <CA+kxMuQifcf23zahp2ALcBZvEcEkuGX9G_GRSs0w2Rk6my=7Zg@mail.gmail.com>
To: Xinchen Hui <laruence@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Bug #69640 Unhandled EngineExceptions thrown from
 userland do not produce any output
From: danack@basereality.com (Dan Ackroyd)

On 15 May 2015 at 14:38, Xinchen Hui <laruence@gmail.com> wrote:
> I'd prefer to
> disallow initializing a engine exception from user land..
>     like if you try to initialize a engine/type/parser exception, an E_ERROR of:
>    what do you think?

Someone reminded me that TypeExceptions are almost certainly going to
be re-used by users for the cases where PHP's type system isn't
powerful enough to handle their use cases:

function handleFooOrBar($instance) {
    if(!$instance instanceof Bar && !$lol instanceof Foo) {
        throw new TypeException('$instance must be either an instance
of Bar or Foo');
    }
    ...
}

Re-using the built-in TypeException for this would be the right thing
to do and so it needs to be creatable in userland.

cheers
Dan