Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109862
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <CALKiJKpjwrdhnQT35myRRC-Sx-kFLzNQ6=a7J-_yEyzFm+2XVA@mail.gmail.com>
Date: Mon, 27 Apr 2020 17:40:17 -0400
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <F519C26E-E65E-46E5-9B70-74259310E774@newclarity.net>
References: <CANOvohpz5OzHZSxdABncBXRQfeF-XnKqpK8BBDQ8OeT+jBL96w@mail.gmail.com>
 <5ea5e72d.1c69fb81.ecd6b.8d05SMTPIN_ADDED_MISSING@mx.google.com>
 <CALKiJKpjwrdhnQT35myRRC-Sx-kFLzNQ6=a7J-_yEyzFm+2XVA@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] [RFC] PHP Namespace Policy
From: mike@newclarity.net (Mike Schinkel)

> On Apr 27, 2020, at 4:25 AM, Rowan Tommins <rowan.collins@gmail.com> =
wrote:
>=20
> To me, the answer to that is quite simple: we have several hundred
> functions, and several dozen classes and interfaces, which are not in =
such
> a namespace; and we have millions of lines of code out in the world =
using
> them. So ... we need a consistent policy on what goes in
> and what stays out.=20

How about a simply policy:  Newer things go in, older ones stay out? =20

Check the docs to see which is which if you are unsure, or just let your =
IDE auto-complete for you.

-Mike=