Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67660 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43095 invoked from network); 8 Jun 2013 19:49:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jun 2013 19:49:13 -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.107 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.107 smtp107.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.107] ([108.166.43.107:33746] helo=smtp107.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 42/01-38360-9BA83B15 for ; Sat, 08 Jun 2013 15:49:13 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 1900B980BC; Sat, 8 Jun 2013 15:49:11 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id A1DC7980B7; Sat, 8 Jun 2013 15:49:10 -0400 (EDT) Message-ID: <51B38AB6.8060809@sugarcrm.com> Date: Sat, 08 Jun 2013 12:49:10 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Nikita Popov CC: Dmitry Stogov , PHP internals References: <51B22397.2050709@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Internal operator overloading and GMP improvements From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > My main interest here is improving the usability of GMP - the operator > overloading is just a means to that goal. With that in mind, I think it I understand that, but operator overloading is not the GMP-only change. It is a change deep in the core of the engine, and as such should be considered as generic engine change. If you did it confined to GMP module, it would be different. > makes little sense to land just the addition of overloading, but leave > the GMP changes out. That's why I'm doing them both in one :) Hope that > makes some sense ^^ I'm sorry, but I disagree. GMP is one thing, and big core changes - introducing operator overloading - is another. GMP refactoring by itself is rather narrow thing, most PHP users don't even use GMP and don't need it. However, introducing operator overloading for objects in PHP is a huge thing with big implications for the future. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227