Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112593
MIME-Version: 1.0
References: <DM6PR07MB661827026586104D5DEDAA64F9C20@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CADyq6sLk-kuSBepYRSBq0nmvMsUBHfDSmMTrpoPjDAbsDath6Q@mail.gmail.com> <DM6PR07MB66181642FB949807BD2AD09BF9DF0@DM6PR07MB6618.namprd07.prod.outlook.com>
In-Reply-To: <DM6PR07MB66181642FB949807BD2AD09BF9DF0@DM6PR07MB6618.namprd07.prod.outlook.com>
Date: Tue, 22 Dec 2020 16:18:07 +0100
Message-ID: <CAFPFaMLC_9cLifcQenntDVWoeHOsUHcB7bZ0rhdBrGfExBdNCA@mail.gmail.com>
To: tyson andre <tysonandre775@hotmail.com>
Cc: Marco Pivetta <ocramius@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a26d0d05b70f1592"
Subject: Re: [PHP-DEV] Straw poll: Naming for `*any()` and `*all()` on iterables
From: george.banyard@gmail.com ("G. P. B.")

--000000000000a26d0d05b70f1592
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 22 Dec 2020 at 16:05, tyson andre <tysonandre775@hotmail.com> wrote=
:

> Hi Marco,
>
> >Hey Tyson,
> >
> > I know I'm being stubborn, but we have namespaces, but also an "old
> guard" that doesn't understand its own programming language =F0=9F=A4=B7=
=E2=80=8D=E2=99=80=EF=B8=8F
>
> I assume it's a case of not liking them or assuming others wouldn't like
> them instead of not understanding them.
> Namespaces for https://www.php-fig.org/psr/psr-4/ has been standard for a
> long, long time.
>
> And attempts to standardize on adopting them have been unpopular -
> https://wiki.php.net/rfc/php_namespace_policy
> Existing internal functionality for working with iterators and arrays is
> in the global namespace.
>
> - E.g. it would be slightly more inconvenient to need to write
> `print(\PHP\get_debug_type($var))` or `use function PHP\get_debug_type;
> ...; get_debug_type($var);`
>   and some developers wouldn't like seeing the extra imports or fully
> qualified names mixed with code that doesn't use namespaces.
> - It's inconsistent for some new categories of functionality to have
> namespaces when others wouldn't - the php namespace policy vote seems to
> indicate there's no consensus on what naming pattern we'd have for
> namespaces.
>
> Even in brand new categories of functionality such as FFI or PhpToken,
> we've went with the global namespace.
>

Small nitpick but FFI classes are under the FFI\ namespace, e.g. FFI\CData
[1]

George P. Banyard

[1] https://www.php.net/manual/en/class.ffi-cdata.php


>
> Regards,
> - Tyson

--000000000000a26d0d05b70f1592--