Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106565
To: internals@lists.php.net
References: <CAF+90c_Ctjja=8fR-uBWL1wDxZge771yMujMhaR_R2seKXciYw@mail.gmail.com>
 <CAOWwgpmsHMjnHuH4tfv_5-0f+pGKv2jJmA5v21FbkdpSHTbTJQ@mail.gmail.com>
Message-ID: <25d774e8-183b-d39c-4ac4-81c1b7770229@gmail.com>
Date: Tue, 13 Aug 2019 10:02:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAOWwgpmsHMjnHuH4tfv_5-0f+pGKv2jJmA5v21FbkdpSHTbTJQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] Namespace-scoped declares, again
From: rowan.collins@gmail.com (Rowan Collins)

On 12/08/2019 09:17, Nicolas Grekas wrote:
> Individual files could declare their package using this style:
> <?php declare(package=MyVendor\MyPackage);
>
> That would be enough to group a set of files together and make them share
> eg some private classes, some optional PHP behaviors, etc.
>
> The right side "MyVendor\MyPackage" would also be a FQCN that PHP would
> autoload as a regular class. The corresponding class would then be the
> place where ppl would declare the engine behavior they want for their
> package (strict types, etc). To enforce this, the engine could require that
> the "MyPackage" class implements some interface/extend some base abstract
> class.


I really like this approach. It allows a package definition file to 
exist, without either the language or the header of each file having to 
define its location.

Importantly, although it would trigger the autoloader if not yet 
defined, the package could be defined in advance, for instance as part 
of a preload directive. It could even be possible to define multiple 
packages in one file, or define them dynamically, using all the existing 
features of the language like require and eval.

On a bikeshedding note, I've never liked the way declare syntax looks, 
so would prefer a new keyword, but the symmetry of replacing <?php 
declare(strict_types=1); with <?php 
declare(package=Something\Defining\StrictOptions); is admittedly quite 
appealing.

Regards,

-- 
Rowan Collins
[IMSoP]