Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68592 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70992 invoked from network); 21 Aug 2013 11:16:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2013 11:16:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=igor@wiedler.ch; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=igor@wiedler.ch; sender-id=unknown Received-SPF: error (pb1.pair.com: domain wiedler.ch from 217.26.49.174 cause and error) X-PHP-List-Original-Sender: igor@wiedler.ch X-Host-Fingerprint: 217.26.49.174 mxout014.mail.hostpoint.ch Received: from [217.26.49.174] ([217.26.49.174:31845] helo=mxout014.mail.hostpoint.ch) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1B/57-11927-091A4125 for ; Wed, 21 Aug 2013 07:16:33 -0400 Received: from [10.0.2.45] (helo=asmtp012.mail.hostpoint.ch) by mxout014.mail.hostpoint.ch with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VC6Or-000GwZ-LE; Wed, 21 Aug 2013 13:16:29 +0200 Received: from [84.73.218.139] (helo=[10.0.1.97]) by asmtp012.mail.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VC6Or-000OMv-Is; Wed, 21 Aug 2013 13:16:29 +0200 X-Authenticated-Sender-Id: igor@wiedler.ch Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) In-Reply-To: <52117598.2070404@sugarcrm.com> Date: Wed, 21 Aug 2013 13:16:08 +0200 Cc: "internals@lists.php.net list" , Michael Wallner Content-Transfer-Encoding: quoted-printable Message-ID: References: <60BF8DD5-FEEA-47D9-834F-6C7FDEF3B879@wiedler.ch> <52117598.2070404@sugarcrm.com> To: Stas Malyshev X-Mailer: Apple Mail (2.1508) Subject: Re: [PHP-DEV] [RFC] Importing namespaced functions From: igor@wiedler.ch (Igor Wiedler) Hi, I just looked into the first issue you mentioned. The following does not = produce a warning either currently: use bar as bar; As such, I would say that it would be inconsistent to produce a warning = for functions. Do you agree? Regards, Igor On Aug 19, 2013, at 3:32 AM, Stas Malyshev = wrote: > Hi! >=20 >> RFC: https://wiki.php.net/rfc/use_function >> Patch: https://github.com/php/php-src/pull/388 >=20 > Looking at the patch: >=20 > 1. use function bar as bar; > does not produce any warning