Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:34472 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49865 invoked by uid 1010); 4 Jan 2008 19:24:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 49847 invoked from network); 4 Jan 2008 19:24:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2008 19:24:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=sam@sambarrow.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sam@sambarrow.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sambarrow.com from 205.234.132.11 cause and error) X-PHP-List-Original-Sender: sam@sambarrow.com X-Host-Fingerprint: 205.234.132.11 scottsdale.servershost.net Received: from [205.234.132.11] ([205.234.132.11:38190] helo=scottsdale.servershost.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/C3-63281-A088E774 for ; Fri, 04 Jan 2008 14:24:58 -0500 Received: from [98.172.154.66] (port=61989 helo=[10.200.100.14]) by scottsdale.servershost.net with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1JAsA4-0008Og-Cv; Fri, 04 Jan 2008 13:24:56 -0600 To: Stanislav Malyshev Cc: internals Mailing List In-Reply-To: <477E8707.8060800@zend.com> References: <477DB7BF.10201@chiaraquartet.net> <20080104105558.GC7861@mint.phcomp.co.uk> <477E5649.2080104@chiaraquartet.net> <1199466070.15292.140.camel@sbarrow-desktop> <1199466701.15292.149.camel@sbarrow-desktop> <477E7AC3.20009@zend.com> <1199472405.15292.181.camel@sbarrow-desktop> <477E822E.30108@zend.com> <1199473569.15292.195.camel@sbarrow-desktop> <477E8707.8060800@zend.com> Content-Type: text/plain Date: Fri, 04 Jan 2008 14:23:22 -0500 Message-ID: <1199474602.15292.210.camel@sbarrow-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - scottsdale.servershost.net X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - sambarrow.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [PHP-DEV] type hinting From: sam@sambarrow.com (Sam Barrow) On Fri, 2008-01-04 at 11:20 -0800, Stanislav Malyshev wrote: > > Ok but if someone inputs an array in the query string i have a problem > > Which problem? OK, you'd have string "Array" instead once you handle it. > If it's a problem, then having "Array" from the start is a problem too. Yes, and the type hint will catch this problem in a second. > > with that. And I said standardized way, ie bool true outputs as "1", > > float 5.20 outputs as "5.2". For objects, toString is a standardized > > output but serialization is not, and for arrays no standardized output > > exists. > > Object serialization is very standardized, it has proper handlers, etc. > As for outputting arrays, indeed, 'Array' is not very meaningful, but > would "Incompatible type is call in function foo() /foo/bar.php line > 123" be better? Yes it would. Because the developer would fix the error upon seeing an error message like that, and avoid the entire future problem. Do you suggest letting the bug go unnoticed until it causes real damage?