Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96121
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c-4CuwgJgBPXbYvEJ0W6k41CfP94Xs-ZyNkUzrecbTzvg@mail.gmail.com>
References: <CAF+90c-4CuwgJgBPXbYvEJ0W6k41CfP94Xs-ZyNkUzrecbTzvg@mail.gmail.com>
Date: Fri, 23 Sep 2016 17:46:53 -0400
Message-ID: <CAEUnE0ermQAuzz5+-pu7njNMrkk5jYDuJ-h1qT7O0ZOMWxb8tw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114df494786409053d33b750
Subject: Re: [PHP-DEV] [RFC] Namespace-scoped declares
From: tendoaki@gmail.com (Michael Morris)

--001a114df494786409053d33b750
Content-Type: text/plain; charset=UTF-8

On Friday, September 23, 2016, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals!
>
> I'd like to propose the ability of specifying declare directives like
> "strict_types" at the namespace level.
>
> The broader context of this proposal is to provide a simple and usable
> mechanism that will allow developers to opt-in to stricter language
> semantics on a per-library (or more specifically, per-namespace) basis,
> thus alleviating backwards compatibility and library interoperability
> concerns for such changes.
>
>     https://wiki.php.net/rfc/namespace_scoped_declares
>
> I don't know whether this is the right solution to this problem, so next to
> the specifics of this proposal, I'm also open to discussing alternative
> approaches, as long such discussions can be held at a reasonably technical
> level (i.e. concrete suggestions rather than vague concepts).
>
> Thanks,
> Nikita
>

Aside from the issues already raised, implementing anything like this would
require reworking how the engine handles namespaces. My understanding is
namespaces are implemented as a set of string replace rules. The namespace
itself is not a structure to php. This prevents things like class privacy,
Java's notion of "protected" and so on.

--001a114df494786409053d33b750--