Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100378
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7F2524B8-BC9C-483B-8A5D-94F177EACBAC@bobs-bits.com>
References: <b92961d5-a34f-737b-896b-0d63da0f7f6b@fleshgrinder.com>
 <CALYT1YqgqKLNyYAMwQ9+uoKC3HKVLA71ZZuGpT6H5OM-4JcV7g@mail.gmail.com>
 <CAL0xaBEj8Gb_Xx2eAqgXqh3ALzDBdX5y4aPFLLQvq85BTJM5JQ@mail.gmail.com> <7F2524B8-BC9C-483B-8A5D-94F177EACBAC@bobs-bits.com>
Date: Tue, 5 Sep 2017 12:54:09 +0300
Message-ID: <CAL0xaBHFXrzV=ZDUfJ5Eo32jpM01sP2_dAURo+0CxrRxyZUxuQ@mail.gmail.com>
To: Stephen Reay <stephen@bobs-bits.com>
Cc: Sammy Kaye Powers <me@sammyk.me>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a113f422c390f2c05586e37db"
Subject: Re: [PHP-DEV] [VOTE] UUID
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a113f422c390f2c05586e37db
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

2017-09-05 12:24 GMT+03:00 Stephen Reay <stephen@bobs-bits.com>:

>
> On 5 Sep 2017, at 14:32, Arvids Godjuks <arvids.godjuks@gmail.com> wrote:
>
> That way the API and
> features can be stabilized.
>
>
> Hi Arvids,
>
> This is exactly why I (and possibly others) are in favour of this being
> implemented as a few functions - the object side of things can then be le=
ft
> to a user land implementation, which is much easier to update and refine.
>
> Cheers
>
>
> Stephen
>
>
I would agree if this was something that was in flux or didn't have a set
in stone standard that is universal across languages, platforms and all
kinds of other software (databases come to mind, some have full-blown
first-class citizen support for them, MySQL is also on the path to
introducing them as field type last I heard too).

This is about making a UUID a first-class citizen and having it universally
available going forward, be able to use it as a type hint, same as
DateTimeInterface is used these days (a lot, actually).

Just provide a procedural-style API together with the OOP one. I recon the
OOP one is gonna be used way more though - every userland implementation I
ever saw used an OOP approach.

Or just start packaging PHP code that is shipped with the interpreter: Ship
the Ramsey\Uuid with 7.3 or some 7.2.x release. That one seems the defacto
standard everyone uses, and it is used in my current project too :) Would
be a perfect segway for the discussion we had on the list a few months ago
about doing parts of the packaged modules in PHP itself.

--=20
Arv=C4=ABds Godjuks

+371 26 851 664
arvids.godjuks@gmail.com
Skype: psihius
Telegram: @psihius https://t.me/psihius

--001a113f422c390f2c05586e37db--