Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106594
To: internals@lists.php.net
References: <CAF+90c_Ctjja=8fR-uBWL1wDxZge771yMujMhaR_R2seKXciYw@mail.gmail.com>
 <CAOWwgpmsHMjnHuH4tfv_5-0f+pGKv2jJmA5v21FbkdpSHTbTJQ@mail.gmail.com>
 <25d774e8-183b-d39c-4ac4-81c1b7770229@gmail.com>
 <5d5298a5.1c69fb81.b4ed1.2d97SMTPIN_ADDED_MISSING@mx.google.com>
 <3db68c5e-54d1-812f-bbf5-1b089cba1bff@gmail.com>
 <5d52f72d.1c69fb81.8f95f.57a1SMTPIN_ADDED_MISSING@mx.google.com>
 <2bcb05d6-abf6-4fcb-599e-eaf4bcd58878@gmail.com>
 <CABdc3Wp+HWtbvab78T47sDuGQbBKkUagk-AL0qS4TO97AaoD6g@mail.gmail.com>
 <182a6bd5-4057-7ba1-2cca-ab0be37e0b75@gmail.com>
 <CABdc3WoJzZGoxcLUzHoam=r+4bs7ED9j4+Oz+=+Jk+d_0S2yXA@mail.gmail.com>
 <72896017-20d0-16af-b188-8500777f947b@gmail.com>
 <CABdc3Wo=9V7=pOSXqBEwfW6+9ZGcMAngnKzgRVvqgiCXBX3AZA@mail.gmail.com>
 <00eea416-23be-6629-2e94-4cfa9f5fcb39@gmail.com>
 <CABdc3Wo9nnwG_Nj8jDUV+X16L1JaEjrmkvsewD7eM60j3Z9vOg@mail.gmail.com>
Message-ID: <29d542e8-bf63-3630-c173-367365a26a1f@gmail.com>
Date: Wed, 14 Aug 2019 11:26:34 +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: <CABdc3Wo9nnwG_Nj8jDUV+X16L1JaEjrmkvsewD7eM60j3Z9vOg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] Namespace-scoped declares, again
From: rowan.collins@gmail.com (Rowan Collins)

On 14/08/2019 11:17, Michał Brzuchalski wrote:
> Following that would introduce unneeded additional directory hierarchy
> level in a usual library
> which uses PSR-4 which is the most used one, right?
>
> /composer.json
> /src/Foo.php
> /src/Foo/  <- all package classes should go here?


That would be one place to put it, yes. But it would be entirely up to 
how people wanted to define their autoloader, that's the beauty of it.

There's no reason something couldn't generate an autoloader that 
essentially said this:

function autoload($name) {
    if ( $name == self::PACKAGE_NAME ) {
       require self::SRC_DIR . '/__packagedef.php';
    } elseif ( str_begins_with($name, self::BASE_NAMESPACE) ) {
       require self::SRC_DIR . str_replace('\\', '/', $name) . '.php';
    }
}

Please don't pick holes in that implementation; my point is, if this was 
how packages were implemented, people would decide how they wanted to 
use it, and PSR-4 would probably be superseded by something which 
accounted for packages existing.

Regards,

-- 
Rowan Collins
[IMSoP]