On Mo, 2019-03-18 at 23:30 +0100, David Zuelke wrote:
>
> It would be really useful for e.g. code check systems, tools like
> Composer, hosting platforms, to inform the user of an upcoming or
> past
> EOM/EOL date, without having to maintain a list of these dates
> separately (by copying from, or
On Tue, Mar 19, 2019 at 11:59 AM Pierre Joye wrote:
> On Tue, Mar 19, 2019, 3:29 PM Nikita Popov wrote:
>
> > On Mon, Mar 18, 2019 at 11:31 PM David Zuelke
> > wrote:
> >
> > > Hi all,
> > >
> > > Would it not be lovely to have, say, two new constants, that contain
> > > the date (ISO, UTC, I
On Tue, Mar 19, 2019, 3:29 PM Nikita Popov wrote:
> On Mon, Mar 18, 2019 at 11:31 PM David Zuelke
> wrote:
>
> > Hi all,
> >
> > Would it not be lovely to have, say, two new constants, that contain
> > the date (ISO, UTC, I guess) of when the running PHP series will be
> > end-of-maintenance
On Mon, Mar 18, 2019 at 11:31 PM David Zuelke
wrote:
> Hi all,
>
> Would it not be lovely to have, say, two new constants, that contain
> the date (ISO, UTC, I guess) of when the running PHP series will be
> end-of-maintenance and end-of-life?
>
> Of course PHP_VERSION_SERIES_EOM_DATE and
Hi!
> It would be really useful for e.g. code check systems, tools like
> Composer, hosting platforms, to inform the user of an upcoming or past
> EOM/EOL date, without having to maintain a list of these dates
> separately (by copying from, or scraping, php.net/eol.php).
Why not create a
Hi all,
Would it not be lovely to have, say, two new constants, that contain
the date (ISO, UTC, I guess) of when the running PHP series will be
end-of-maintenance and end-of-life?
Of course PHP_VERSION_SERIES_EOM_DATE and PHP_VERSION_SERIES_EOL_DATE
are a little verbose, but...
It would be
