Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99153 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28971 invoked from network); 24 May 2017 17:02:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 May 2017 17:02:54 -0000 Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:30219] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 73/AD-10292-EBCB5295 for ; Wed, 24 May 2017 13:02:54 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3wXzGy6hYvzXMp for ; Wed, 24 May 2017 19:02:50 +0200 (CEST) To: internals@lists.php.net References: Message-ID: Date: Wed, 24 May 2017 19:02:50 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] [Discussion] UUID From: lists@rhsoft.net ("lists@rhsoft.net") Am 24.05.2017 um 18:35 schrieb Christoph M. Becker: > On 24.05.2017 at 18:25, Remi Collet wrote: > >> Le 24/05/2017 à 17:57, Levi Morrison a écrit : >> >>> I understand the user experience improvement for having a package for UUIDs >>> in core; I'd like that myself. I just want to know why we haven't discussed >>> the existing UUID package and made a new one. >> >> I agree here, why a new extension ? >> >> And I also think using system libuuid is better than reinventing the >> wheel, and having to maintain a uuid algo, when already maintained by >> someone else, which only work on these algo. > > What about Windows support? in times of virtualization and containers i personally would go so far and question the need for support windows native at all which would lead to a much smaller and cleaner codebase and less maintainance overhead (not only for PHP)