Results for project PHP master, build date 2017-04-18 19:26:26-07:00
commit: 847b362
previous commit:1837eea
revision date: 2017-04-18 11:33:06-07:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
>
> I apologise if I've been harsh, but I am truly disappointed. I tried to
> sway the RFC in a certain direction, that is conveying the pretty basic
> notion that using floating points for fixed precision numbers is wrong:
> there's lots of literature on that and especially why floats shouldn't
>
Hi Adam,
On 19/04/2017 18:08, Adam Baratz wrote:
> I am trying to be as thorough as possible in addressing your concerns.
> That's why, after your last response, I delayed the vote and took the
> time to work out how each API differentiates between floating point and
> fixed-precision values. I'm
Hi everyone,
The RFC for making *number_format()* consistent when dealing with negative
zero is now in the voting phase.
Voting will be open for 2 weeks and will close at 0:00 UTC on Wednesday 3rd
May.
https://wiki.php.net/rfc/number_format_negative_zero
Thanks,
Craig
Hi,
Thanks for allowing everyone the time to look at the RFC changes before
> opening the vote ;)
>
I didn't think I needed to extend discussion for the changes I made. The
substance of the proposal hasn't changed. I just responded to your
criticism that there'd need to be a separate type for fix
Hi Adam,
On 18/04/2017 18:58, Adam Baratz wrote:
> I looked more closely at each of the APIs. My conclusion was that a single
> type will be appropriate for floats, doubles, and fixed-precision. I
> updated the RFC with details. If it's accepted, it could be worth including
> some of this content
