Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88984
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.178 as permitted sender)
MIME-Version: 1.0
Date: Wed, 28 Oct 2015 22:57:07 -0400
Message-ID: <CAFp73XuG9PfYv448muxijyk7MS5xG7J5zxz021YQPtAReYvkyQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e015374ec8fb64d052335785f
Subject: Support execution scope realization at runtime (or last pieces for
 private class support)
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--089e015374ec8fb64d052335785f
Content-Type: text/plain; charset=UTF-8

Hi internals!

I want to revive an old patch I was working on last year, and open for
discussion the last missing piece to make it fully complete, allowing me to
write a RFC.

Link to patch introducing support to private classes:
https://github.com/php/php-src/pull/947

Currently, there's no way to determine at runtime what is the scope of the
execution. This means you can't resolve if the current instruction is
happening on a top-level scope, in a class definition, namespace, function
or method.

Together with this (maybe even more importantly), there's no way to resolve
namespaces in any way, since they only exist up to compile time (they
become part of class name through string append), and no real data
structure around it exists. I was forced to create a weird string check to
make it work... =(

I wonder what would be necessary to make this patch possible, if there's
any interest to move this forward and potentially target it for 7.1 release.

Regards,

-- 
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--089e015374ec8fb64d052335785f--