Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71200 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67739 invoked from network); 16 Jan 2014 23:07:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jan 2014 23:07:57 -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 108.166.43.75 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.75 smtp75.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.75] ([108.166.43.75:55275] helo=smtp75.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/C7-21406-C4668D25 for ; Thu, 16 Jan 2014 18:07:56 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B60741E80CB; Thu, 16 Jan 2014 18:07:53 -0500 (EST) X-Virus-Scanned: OK Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 611291E812D; Thu, 16 Jan 2014 18:07:53 -0500 (EST) Message-ID: <52D86648.5010600@sugarcrm.com> Date: Thu, 16 Jan 2014 15:07:52 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Sara Golemon , Andrey Andreev CC: "internals@lists.php.net" References: <52D83F13.3000702@ajf.me> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Introducing "Array Of" RFC From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > If PHP were to follow HHVM's syntax, we'd get the type-checker as a > freebie. (If and when we took on return and scalar type hints as > well) I'm pretty sure if such tool were open source, it would not be hard to patch it to follow any syntax, provided underlying sematics is the same. It probably parses the code into some kind of internal representation anyway, so by slightly changing that parser you will be able to accommodate any syntax. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227