Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75594
Return-Path: <rowan.collins@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 22595 invoked from network); 16 Jul 2014 17:58:46 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Jul 2014 17:58:46 -0000
Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.176 as permitted sender)
X-PHP-List-Original-Sender: rowan.collins@gmail.com
X-Host-Fingerprint: 74.125.82.176 mail-we0-f176.google.com  
Received: from [74.125.82.176] ([74.125.82.176:60091] helo=mail-we0-f176.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 80/A3-31820-55DB6C35 for <internals@lists.php.net>; Wed, 16 Jul 2014 13:58:45 -0400
Received: by mail-we0-f176.google.com with SMTP id q58so1319372wes.35
        for <internals@lists.php.net>; Wed, 16 Jul 2014 10:58:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=Xscx3pBdSx0+ACOSURfjEc4jhsy2OHhfZHYg9ByH8SQ=;
        b=fVKRCsUGRvYVCiq5JXRQN2pLIUV8E1XmObKGlDKMt51z0vCp7twu11hPHZxr0Eq0/Z
         MycdD7mjLnE/7AfBW0+2S9UdVKbeJ85/SgMp0KelBllQ4oeGZtx9RnnwSz6POCt8LrTo
         ob/VE8SdjJWduk7H2rYCWXhUmVCiZsbM/xjR1uIqSfm3MRa1a5eCUzuAn1UfxYr3RMAe
         GU/6yPOij1UWEW85W4X57anHdcyLK5nRf+wHClQOxfbtkkLH8MNVVIChKYvmzGRR1FiQ
         PhcLOzsyhGWHJRvuyirxmaCIGDx1EAXIye36BLlBDfpJ35O3lOyX36yIC6HllZhDqsvo
         yKbQ==
X-Received: by 10.180.85.162 with SMTP id i2mr15654244wiz.53.1405533522369;
        Wed, 16 Jul 2014 10:58:42 -0700 (PDT)
Received: from [192.168.0.139] ([62.189.198.114])
        by mx.google.com with ESMTPSA id ft17sm83707wjc.14.2014.07.16.10.58.40
        for <internals@lists.php.net>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 16 Jul 2014 10:58:41 -0700 (PDT)
Message-ID: <53C6BCD2.4020605@gmail.com>
Date: Wed, 16 Jul 2014 18:56:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAGa2bXZDZXWaNBRA-JNNqmO5+-JFxvROwhTDLiJqfZWrF-NWow@mail.gmail.com>
In-Reply-To: <CAGa2bXZDZXWaNBRA-JNNqmO5+-JFxvROwhTDLiJqfZWrF-NWow@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Use of php_mt_rand() rather than php_rand()
From: rowan.collins@gmail.com (Rowan Collins)

Yasuo Ohgaki wrote (on 16/07/2014):
> The only BC issue I can think of is game that expects the same pseudo
> random sequences. These apps may use mt_srand() to get fixed random
> sequences and adjust their apps if it is needed. This is acceptable BC
> for new releases. IMO.

Do you propose making rand() a synonym for mt_rand()? If so, wouldn't it 
make sense for srand() to become a synonym for mt_srand()?

Or are you saying that there are functions other than rand() which can 
currently be seeded by srand(), and these would be affected by 
mt_srand() instead? If so, that seems like a pretty subtle change to 
document and publicise.