Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100377
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CALYT1YqgqKLNyYAMwQ9+uoKC3HKVLA71ZZuGpT6H5OM-4JcV7g@mail.gmail.com>
References: <b92961d5-a34f-737b-896b-0d63da0f7f6b@fleshgrinder.com> <CALYT1YqgqKLNyYAMwQ9+uoKC3HKVLA71ZZuGpT6H5OM-4JcV7g@mail.gmail.com>
Date: Tue, 5 Sep 2017 10:32:20 +0300
Message-ID: <CAL0xaBEj8Gb_Xx2eAqgXqh3ALzDBdX5y4aPFLLQvq85BTJM5JQ@mail.gmail.com>
To: Sammy Kaye Powers <me@sammyk.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="f40304360c6811e38905586c3c75"
Subject: Re: [PHP-DEV] [VOTE] UUID
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--f40304360c6811e38905586c3c75
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

2017-09-04 19:03 GMT+03:00 Sammy Kaye Powers <me@sammyk.me>:

> I really, really wanted to vote yes for this as I've wanted simple
> UUID creation in core for a long time, but I can't agree this is the
> correct implementation. Something like "uuid_v4_create()" seems to
> make a lot more pragmatic sense and use ramsey/uuid for anything more
> complicated.
>
> Sorry Richard, but I'm -1 on this one. But thanks for putting in all
> the effort! I think another attempt with a simpler API &
> implementation could be a winner! :)
>
> Thanks,
> Sammy Kaye Powers
> sammyk.me
>
>
Hello everyone, it's been a while.

As a userland dev, I completely agree with the RFC. The implementation
details may be worked out a bit, but having UUID's as an object is a good
thing and having a proper reference implementation that follows the
standard to the letter is very valuable. UUID's are a universal concept,
used in so many systems across the IT world, that I personally consider
them to be a thing on their own. I do believe they deserve to be an object
- if you expect a UUID, you want a very specific thing, not just a generic
string and then validate it every time with some form of
"is_valid_uuid($uuid)". Even if PHP will have a reference implementation,
99.9% chance I will use a wrapper library that will give me an object I can
work with. And not only for my personal preference, but also so other
people working on the same project do not mess with a UUID string. Type
hinting checks are also quite important, that I learned first hand lately
as I went PHP 7.1 strict_types=3D1 on my whole codebase - I have been passi=
ng
crap to in places that I would have never known, and probably would never
result in an issue due to the nature of the error.

I do, however, think that maybe doing a userland PHP implementation of the
proposed module, so people can play and use it and then converting it to a
PHP C module closer to 7.3 would be a better way. That way the API and
features can be stabilized.

--=20
Arv=C4=ABds Godjuks

+371 26 851 664
arvids.godjuks@gmail.com
Skype: psihius
Telegram: @psihius https://t.me/psihius

--f40304360c6811e38905586c3c75--