Re: Input on deprecating PSR-0
| From: | Remi Collet | Date: | Fri, 10 Oct 2014 07:00:35 +0000 |
| Subject: | Re: Input on deprecating PSR-0 | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-55425@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 09/10/2014 15:10, Brett Bieber a écrit :
> Greetings,
>
> The PHP Framework Interoperability Group has called for a vote to
> deprecate PSR-0 in favor of PSR-4.
I really don't see how this can help.
PEAR library are not compatible with PSR-4, so PSR-0 with is
compatibility clause will stay for a very long time.
More, PSR-0/PSR-4 have a nice clause
The fully qualified class name MUST have a top-level namespace
name, also known as a "vendor namespace".
This is useful, at least to avoid namespace collision.
But it seems (at least to me), that a very few people have read /
understood this part, and doesn't use any top level "Vendor" directory.
And for downstream distribution, all PSR-4 libraries have to be
installed to a restored PSR-0 path (with full namespace)
So big -1 from me
Remi.
> I'd like to get the thoughts on this from the PEAR community before
> casting our vote.
>
> For more information and background, please see their Google
> Group:
> https://groups.google.com/forum/#!topic/php-fig/7g6n145XlbI
>
> Thanks,
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlQ3hBIACgkQYUppBSnxahhnRACguZwqFR+dtV/d8K0BAOq793iu
aR0AoKXOkbk5CJsVlsG7XOEcUSILqz0M
=GceH
-----END PGP SIGNATURE-----