Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44649 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41512 invoked from network); 2 Jul 2009 13:42:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jul 2009 13:42:13 -0000 Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.206 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: kalle.php@gmail.com X-Host-Fingerprint: 209.85.218.206 mail-bw0-f206.google.com Received: from [209.85.218.206] ([209.85.218.206:53277] helo=mail-bw0-f206.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/75-16153-439BC4A4 for ; Thu, 02 Jul 2009 09:42:12 -0400 Received: by bwz2 with SMTP id 2so1089054bwz.23 for ; Thu, 02 Jul 2009 06:42:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=prxDtMYFbNHYhDpXCjkE5/qBHGnl1w71CMP2r1nuDp4=; b=ee4PF4FgcCk09CIbc8aiyaeTtW4ehxpmqoJRDopqL2VR7ILzgy8YjkzgVjcI+WVvYm knIPrQdZ6dqvUjWsZVrscR6/zCClyUji0b/bJPzMt4lynbsY52wbbsL4Bly40ucu15Y1 K4JmEen8Gw6NnHZWvsFcFhI+zDjejEKotEdDA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=vajIGKENENZyEwhDFcktvZ4VpdcQ9gYLJnYqBLhPlShcFAWszVF5PVELIbB6/nsnUj t0lnviMAcdsGZEhf6xuORNoaBzJA2nftcj0wiaUAS7WHMn8PHBBrM+snSMM5tAWcrt72 43Oi7/he3HVGRiKXdIhvW9kUGTLiHm20nrlTo= MIME-Version: 1.0 Sender: kalle.php@gmail.com Received: by 10.204.71.82 with SMTP id g18mr56115bkj.120.1246542129257; Thu, 02 Jul 2009 06:42:09 -0700 (PDT) In-Reply-To: <4A4CA264.8030009@interjinn.com> References: <4A4C7CE6.6070107@gmail.com> <7f3ed2c30907020356s45fd2c56l30b77e92fec61a8c@mail.gmail.com> <4A4C9A8F.4060107@gmail.com> <4A4CA264.8030009@interjinn.com> Date: Thu, 2 Jul 2009 15:42:09 +0200 X-Google-Sender-Auth: 0ba25335dac65f80 Message-ID: <2dedb8a0907020642o721605d4wa2ea7c4bf6e474d6@mail.gmail.com> To: Robert Cummings Cc: "Ionut G. Stan" , PHP internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: Type hinting revisited for PHP 5.3 From: kalle@php.net (Kalle Sommer Nielsen) 2009/7/2 Robert Cummings : > Ionut G. Stan wrote: > I think it should be E_WARNING with auto type juggling if bad data comes > through. This way it behaves as normal PHP code does without special > handling to mitigate a script failure. The log files will still alert you to > the problem, and if you really want an exception handler then you still have > that option. It should be an E_RECOVERABLE, as it would make most sense, the error is recoverable as it did not leave the engine in a state that it cannot continue from a technical standpoint. -- regrads, Kalle Sommer Nielsen kalle@php.net