Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92226
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.52 as permitted sender)
MIME-Version: 1.0
References: <570C9101.5060500@php.net> <CAJaRsPvzG8iVm3O2Nz5k=djt0e2HqB-jmQBDb8BysbxfvfhUFg@mail.gmail.com>
 <CAEZPtU5UKB06TofSdiwNyKUm75y9o7YKbsA8i=9=i4=EZxGfgQ@mail.gmail.com>
In-Reply-To: <CAEZPtU5UKB06TofSdiwNyKUm75y9o7YKbsA8i=9=i4=EZxGfgQ@mail.gmail.com>
Date: Tue, 12 Apr 2016 13:30:20 +0000
Message-ID: <CAJaRsPvVaMJJA-zoj1A3Tjf+F--b2gg6oGvqKQuD4pSfhffjDQ@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: PHP internals <internals@lists.php.net>, Sebastian Bergmann <sebastian@php.net>
Content-Type: multipart/alternative; boundary=94eb2c0433c037e86b053049aad4
Subject: Re: [PHP-DEV] UUID
From: colinodell@gmail.com ("Colin O'Dell")

--94eb2c0433c037e86b053049aad4
Content-Type: text/plain; charset=UTF-8

>
> I would prefer not to refer to random to avoid any confusion with the
> recent added random function. As uuid is not crypto safe and is not aimed
> to. Users will then hopefully not think about using instead of the random
> api.
>
> Also uuid alone may be a problem (bc?) It sounds like a logical choice.
> Alternatively uuid_create ().
>
Ah yes, good point.  I was thinking random_uuid() might be good for v4
UUIDs, and that a parameter might be needed, but I failed to make the
connection that not all UUID versions are random - my apologies for not
catching that before hitting send.

I like the idea of uuid() or uuid($version = 4)

--94eb2c0433c037e86b053049aad4--