Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94441 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 782 invoked from network); 9 Jul 2016 08:19:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jul 2016 08:19:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.48 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 209.85.215.48 mail-lf0-f48.google.com Received: from [209.85.215.48] ([209.85.215.48:35526] helo=mail-lf0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/59-18622-D73B0875 for ; Sat, 09 Jul 2016 04:19:10 -0400 Received: by mail-lf0-f48.google.com with SMTP id l188so40999624lfe.2 for ; Sat, 09 Jul 2016 01:19:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Z2unlM28pzH01E4FU63E0NMgUqwuq+LjUBam8ey3XEs=; b=Aun/nsAtXCKbZKnSPo4G2fLXMpO9lYuektRE4M9vqJSn60NP9Mbkea4y+8ZQzauOGA VZJEKfXvJNJseXEKJe244eBE97hHPmbqJPVducqrGY0xAfxHWfWj/9K07HPZ94nf7r+9 S3iMUQCH4ChblbyanTpNyKKnjBSngvK12htY0UrTC2i9G+QInFRhWQNxtl9w/1hoI7qV 1sOUl+DCdRWJFL8S2Y6vByga+Kid89c0vaL2HLmaiCHUkzMSRiaCxdoXN1ya7zPQskxD U997WG5kEdIxsJ13AYqZ/GGPIXMbvw1Gj4lVLPBEdH7+VL+05X8PmZL/E9/USTyUKLKu myZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Z2unlM28pzH01E4FU63E0NMgUqwuq+LjUBam8ey3XEs=; b=XPYyvVcL+LiZsu/pr9VJckojOY3nsHi4/VPW3d+MkykqX3R78Sj+r8e0pbM+LzYSaf EjOsj/wt1Eo1+64NslC7ui3lXzVpDmmTHAyPFuk5uiuqowzJGaUtSfgb5H+OF+QgaEEq YUCpaioo8kxhZDEOL+FNJaKlbvHm/6Ej8HaTlnWqh1OlovkdFBZGh10+JML8Ibb6r1L8 vmKZJixR/7tYwYD8lZ0aF49wbmHcxvA4kP2rHlQySxLuKntyU+kz37eFEsL4vIRnlz1M zyx1WkiuPSBGh3ozzLi9eCuprmvcxcFxLCgb+uuZ+ygviiMkAxLJDcpL1CILY4BKRo1A fWqQ== X-Gm-Message-State: ALyK8tLnxkOkb6KY4s+oPqL0eaLwd8eT2fuBsvBGxfcIt9JZz9DAeRuROj+hnsEbjWGqgNi0+DKZU2lgemBzcw== X-Received: by 10.46.71.3 with SMTP id u3mr2560150lja.67.1468052345387; Sat, 09 Jul 2016 01:19:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 09 Jul 2016 08:18:55 +0000 Message-ID: To: Pierre Joye Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11411c0e8effd705372f924d Subject: Re: [PHP-DEV] [RFC][VOTE] RNG fixes From: leight@gmail.com (Leigh) --001a11411c0e8effd705372f924d Content-Type: text/plain; charset=UTF-8 On Sat, 9 Jul 2016 at 08:48 Pierre Joye wrote: > So, I voted no then as it is clear that you do not see a problem to > break codes without a single warning or time to adapt before. > > The other sections are fine and voted yes. > For the part where you voted no. Still nobody has presented (publicly available) source that makes legitimate use of mt_srand (yes it's mt_srand that is "broken" here, not mt_rand) for deterministic streams of random numbers. I can only assume by this that almost nobody does. However, for those that do, they can still use the old algorithm. For all of the other sections where you voted yes, they are mostly bug fixes, but all change the output of mt_rand AND more functions (without a single warning, like you wanted). I'm not trying to encourage you to change any votes, but I need to make sure you understand what you're voting for. --001a11411c0e8effd705372f924d--