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 sorry if it seems like I'm trying to force > this through. I'm just trying to avoid spinning tires when it seems like > we're likely to "agree to disagree." > > That said, I'm not sure how to respond to you when your feedback is very > brief. Simply calling something "ill-advised" doesn't give me a lot to > go on, especially when I feel like I provided a pretty rich level of > detail in the RFC.
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 be used to represent money. The result was instead "floats all the things!", which is indeed the opposite of what I was expecting. > I'd like to get a better handle on how we should discuss RFCs. We seem > to hit impasses pretty frequently. If you have any specifics on what's > helpful for you, I'm happy to adjust my style. I have no specific suggestion. I'm just worried about the potential disruptions of features that benefit a tiny portion of our users. While I'm at it, could you please clarify the following for me: Why is there so much effort devoted to the legacy dblib driver when pdo_sqlsrv seems a much better replacement on paper? Googling for info didn't help, so there surely must be something I'm missing here. Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
