Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68297 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25659 invoked from network); 24 Jul 2013 07:18:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jul 2013 07:18:49 -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.83 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.83 smtp83.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.83] ([108.166.43.83:43205] helo=smtp83.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 95/22-07084-8DF7FE15 for ; Wed, 24 Jul 2013 03:18:48 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 1485E500DF; Wed, 24 Jul 2013 03:18:46 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id B75AE500CB; Wed, 24 Jul 2013 03:18:45 -0400 (EDT) Message-ID: <51EF7FD5.9090300@sugarcrm.com> Date: Wed, 24 Jul 2013 00:18:45 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Yasuo Ohgaki CC: "internals@lists.php.net" References: <60BF8DD5-FEEA-47D9-834F-6C7FDEF3B879@wiedler.ch> <51EF593D.5080005@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Importing namespaced functions From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I don't have concrete idea right now. If there is cleaver way that > avoids disadvantages, I would like to see such feature by default > since almost all PHP competitors have this. We are not in competition with other languages over number of features implemented. "All cool boys do it" is not really a good answer, the good answer should be why is it good for PHP as a language and as an ecosystem having particular target audience and particular purpose. In my opinion, changing what classes do in runtime fits the PHP's traditional audience and purposes rather poorly. Of course, there are always non-traditional ways of using it, it is a time-honored way of hackers. For them, there's always runkit. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227