Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67276 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48571 invoked from network); 2 May 2013 21:55:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 May 2013 21:55:30 -0000 Authentication-Results: pb1.pair.com header.from=igor@wiedler.ch; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=igor@wiedler.ch; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain wiedler.ch from 217.26.49.180 cause and error) X-PHP-List-Original-Sender: igor@wiedler.ch X-Host-Fingerprint: 217.26.49.180 mxout001.mail.hostpoint.ch Received: from [217.26.49.180] ([217.26.49.180:64429] helo=mxout001.mail.hostpoint.ch) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id ED/F1-37535-1D0E2815 for ; Thu, 02 May 2013 17:55:30 -0400 Received: from [10.0.2.20] (helo=asmtp002.mail.hostpoint.ch) by mxout001.mail.hostpoint.ch with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1UY1TK-000FpT-Dy; Thu, 02 May 2013 23:55:26 +0200 Received: from [84.73.218.139] (helo=[10.0.1.96]) by asmtp002.mail.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1UY1TK-00004e-B7; Thu, 02 May 2013 23:55:26 +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.3 \(1503\)) In-Reply-To: Date: Thu, 2 May 2013 23:55:25 +0200 Cc: "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <4A468FA3-3260-463C-9D4E-FA78736447C1@wiedler.ch> References: <94D5D345-4D14-4BFF-9650-15E80205A6DE@wiedler.ch> To: Sebastian Krebs X-Mailer: Apple Mail (2.1503) Subject: Re: [PHP-DEV] Re: Importing namespaced functions From: igor@wiedler.ch (Igor Wiedler) No, I want to keep autoloading out of this proposal. It is way beyond = the scope of the namespacing issue and also incredibly complex. That said, this RFC may be useful for implementing autoloading in the = future, as it addresses one of the things that makes function = autoloading hard, which is being able to distinguish between namespaced = and global function calls. But that's only one piece of the puzzle. On May 2, 2013, at 11:40 PM, Sebastian Krebs = wrote: > Hi, >=20 > Are you going to cover autoloading of functions too? >=20 > Regards, > Sebastian