Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78246 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95895 invoked from network); 22 Oct 2014 20:11:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2014 20:11:25 -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.99 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.99 smtp99.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.99] ([108.166.43.99:47180] helo=smtp99.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F8/E5-63701-C6F08445 for ; Wed, 22 Oct 2014 16:11:24 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp13.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id C9A44380626; Wed, 22 Oct 2014 16:11:21 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp13.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 5A66C38062D; Wed, 22 Oct 2014 16:11:21 -0400 (EDT) X-Sender-Id: smalyshev@sugarcrm.com Received: from Stass-MacBook-Pro.local ([UNAVAILABLE]. [74.85.23.222]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.2.13); Wed, 22 Oct 2014 20:11:21 GMT Message-ID: <54480F68.6010406@sugarcrm.com> Date: Wed, 22 Oct 2014 13:11:20 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Andrea Faulds CC: Zeev Suraski , Dmitry Stogov , PHP Internals References: <66B7B28C-2651-4A71-AC2A-55D4C7BB3DDC@ajf.me> <866A39C7-6F11-408D-8BCA-594BA22E8569@ajf.me> <5447682B.2080100@sugarcrm.com> <019325A5-4F82-4179-B4D7-29E5649B2616@ajf.me> <54480580.9040302@sugarcrm.com> <4F848DB0-0266-46A0-9805-2B2BF22CAC33@ajf.me> In-Reply-To: <4F848DB0-0266-46A0-9805-2B2BF22CAC33@ajf.me> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Safe Casting Functions From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Yes, that’s still merely an implementation detail. If HHVM decides to > make explode() into an opcode, it’s not a language change. It is not > any different if PHP does the same. If HHVM decides to introduce new type handling rules, however, it is. Even if they are going to be called using ( and ). >> You propose to add completely new type conversion rules into the >> engine, in addition to ones already present and used there. It's >> not the same as merely changing how the engine internally runs >> pre-existing code. The new rules are definitely becoming major part >> of the language, not an implementation detail of some random >> function like str_pad. > > No, they’re just a set of new validation functions. No, they are not. They are new engine primitives for handling type conversions. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/