Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52106 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14361 invoked from network); 30 Apr 2011 17:26:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Apr 2011 17:26:47 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.193 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.193 smtp193.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.193] ([67.192.241.193:36515] helo=smtp193.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EB/B1-10915-5564CBD4 for ; Sat, 30 Apr 2011 13:26:47 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp9.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id C8F973C01B4 for ; Sat, 30 Apr 2011 13:26:42 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp9.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 84A463C01AF for ; Sat, 30 Apr 2011 13:26:42 -0400 (EDT) Message-ID: <4DBC4652.6000703@sugarcrm.com> Date: Sat, 30 Apr 2011 12:26:42 -0500 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: internals References: <4DB923E6.3020307@sugarcrm.com> <4DB9A7BE.6010307@sugarcrm.com> <20110428181630.GA8496@phcomp.co.uk> <4DBA46FD.5090106@sugarcrm.com> <20110429085533.GF8496@phcomp.co.uk> In-Reply-To: <20110429085533.GF8496@phcomp.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Return type-hint From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Which a good compiler with time to burn (think HipHop not Zend) could do, eg: 1. I think you overestimating the capabilities of HipHop, but I can be mistaken. 2. HipHop represents a minority of use cases for PHP, I do not think it is practical for PHP to target only monolitic pre-compiled applications. At least until it has proven in the field that this is a better model. In fact, if I am mistaken and this is so popular, why HipHop people don't introduce strict typing in their PHP and see how it goes? If it gets popular, great. If not, no harm done. Since they don't rely on Zend Engine anyway, AFAIK, keeping up with the patches in not really a question, so I don't see why it can't be done at any time. > And it will. > Objects are a big thing in the language - but their use is not mandated, > many programs don't use them. Right. But objects are done comprehensively, not by adding a little piece here and there. We had such thing in PHP 4, and it didn't really work until we redid it in PHP 5. Same with strict typing - you have to do the full thing to make it really useful. Serving just one use case is bad in the long run. I think adding full strict typing is not the way to go for PHP. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227