Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101324
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.216.182 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CAF+90c_Ctjja=8fR-uBWL1wDxZge771yMujMhaR_R2seKXciYw@mail.gmail.com>
References: <CAF+90c_Ctjja=8fR-uBWL1wDxZge771yMujMhaR_R2seKXciYw@mail.gmail.com>
Date: Mon, 11 Dec 2017 10:46:34 -0500
Message-ID: <CAESVnVo8Z9SEaBV4+TALvLntuHxhCWf0-rpkRjWRjcidsLnunQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Namespace-scoped declares, again
From: pollita@php.net (Sara Golemon)

On Mon, Dec 11, 2017 at 8:43 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> Some time ago I introduced the following proposal for namespace-scoped
> declares:
>
>     https://wiki.php.net/rfc/namespace_scoped_declares
>
> The idea is to allow specifying declare directives for a whole library or
> project using:
>
>     namespace_declare('Vendor\Lib', ['strict_types' => 1]);
>
> I've finally gotten around to implementing this proposal (
> https://github.com/php/php-src/pull/2972) and would like to move forward
> with it.
>
Being lazy here because I'm literally on my way out the door and don't
have a moment to parse through the implementation, but can you clarify
how this impact compile-time declares?

<?php

require('a.php");
require('b.php"); // This file has a namespace declaration
require('c.php");

In this example, does a.php wind up getting compiled with a different
set of declares than b.php and c.php?

-Sara