Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61170 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12530 invoked from network); 12 Jul 2012 16:30:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jul 2012 16:30:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.153 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.153 smtp153.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.153] ([67.192.241.153:47187] helo=smtp153.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FA/10-11045-7BBFEFF4 for ; Thu, 12 Jul 2012 12:30:47 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id B1E0C580EA; Thu, 12 Jul 2012 12:30:44 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp5.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 64D265863C; Thu, 12 Jul 2012 12:30:44 -0400 (EDT) Message-ID: <4FFEFBB3.7090507@sugarcrm.com> Date: Thu, 12 Jul 2012 09:30:43 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Anthony Ferrara CC: "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Iterable Type Hint From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Would it be worth while adding a new type hint that checks for this > condition? I'd propose Iterable: I see more and more multiplication of weird ad-hoc type checks. First we had "callable", now "traversable", then we invent more and more weird functional types with complex logic. I don't like this development at all. It's ad-hoc introducing of half-baked, unstandartized, undesigned strict typing. Strict typing is not a good idea for PHP, and weird strict typing based on complex conditions hidden from the user is even worse IMO. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227