Re: [PHP-DEV] RFC: mt_* functions

2001-08-05 Thread Jeroen van Wolffelaar
> > Both function families are the same in syntax & returning, only the > > algorithm is different. I.e.: the semantics is the same. The algorithm - if > > correct - shouldn't bother, and shouldn't be the concern of the programmer, > > but rather the system maintainer (specific cases excluded, but

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Rasmus Lerdorf
> >Sure, although rand() tends to be the same everywhere as well. At least > >on all the systems I care about it is the same. Linux, FreeBSD, OpenBSD > >and Solaris all seem to use the same algorithm. > > Then why do some people have troubles with rand() on Solaris? :) > Or is it some specific v

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Jani Taskinen
On Sat, 4 Aug 2001, Rasmus Lerdorf wrote: >> On Sat, 4 Aug 2001, Rasmus Lerdorf wrote: >> >based on their seeds. If I, as an application developer, distributes a >> >regression test harness which tests my app with a specific seed expecting >> >a specific sequence and the server my app runs on ha

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Rasmus Lerdorf
> On Sat, 4 Aug 2001, Rasmus Lerdorf wrote: > >based on their seeds. If I, as an application developer, distributes a > >regression test harness which tests my app with a specific seed expecting > >a specific sequence and the server my app runs on has switched rand() to > >use the mt_rand() algor

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Jani Taskinen
On Sat, 4 Aug 2001, Rasmus Lerdorf wrote: >based on their seeds. If I, as an application developer, distributes a >regression test harness which tests my app with a specific seed expecting >a specific sequence and the server my app runs on has switched rand() to >use the mt_rand() algorithm my re

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Rasmus Lerdorf
> Both function families are the same in syntax & returning, only the > algorithm is different. I.e.: the semantics is the same. The algorithm - if > correct - shouldn't bother, and shouldn't be the concern of the programmer, > but rather the system maintainer (specific cases excluded, but than yo

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Jeroen van Wolffelaar
> Please don't. Ini settings that change semantics are a bother, and > people should be able to choose their random function. Both function families are the same in syntax & returning, only the algorithm is different. I.e.: the semantics is the same. The algorithm - if correct - shouldn't bother

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Sterling Hughes
At 11:15 PM 8/4/2001 +0200, Stig Sæther Bakken wrote: >[<[EMAIL PROTECTED]>] > > Hi, > > > > Currently, the rand_functions all have mt_ clones, which use a > > in-PHP-implementation (Mersenne-Twister) rather than an external > > implementation. > > > > This is IMHO a bit strange way of chosing bet

Re: [PHP-DEV] RFC: mt_* functions

2001-08-04 Thread Stig Sæther Bakken
[<[EMAIL PROTECTED]>] > Hi, > > Currently, the rand_functions all have mt_ clones, which use a > in-PHP-implementation (Mersenne-Twister) rather than an external > implementation. > > This is IMHO a bit strange way of chosing between implementation. My > suggestion is to make it only one familiy

[PHP-DEV] RFC: mt_* functions

2001-08-04 Thread jeroen
Hi, Currently, the rand_functions all have mt_ clones, which use a in-PHP-implementation (Mersenne-Twister) rather than an external implementation. This is IMHO a bit strange way of chosing between implementation. My suggestion is to make it only one familiy of functions, the implementation of w