Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98922 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81592 invoked from network); 1 May 2017 21:37:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 May 2017 21:37:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam.baratz@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adambaratz@php.net; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.179 as permitted sender) X-PHP-List-Original-Sender: adam.baratz@gmail.com X-Host-Fingerprint: 209.85.220.179 mail-qk0-f179.google.com Received: from [209.85.220.179] ([209.85.220.179:32986] helo=mail-qk0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/32-01540-D7AA7095 for ; Mon, 01 May 2017 17:37:01 -0400 Received: by mail-qk0-f179.google.com with SMTP id u68so18468559qkd.0 for ; Mon, 01 May 2017 14:37:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=AnWZSIym/3nKpkASOHy+407T3Es8Y8BQ4mWWuFgXfKw=; b=h0IgmGgkJ7hqMcQCwDMzjnQUUBVd/hqhb8zcTIBB/CASaZuaKPOqluDMukyVOo2b2c vIkJTi9vEPq2HhH0J5bkGeEMnfreElIGB0Uh2YuuEv9ss9BJeRbXX72YZYZQvsIYP3Ao JyfmbE01mylTaYSxZoMYaCojqbTw8nXPJtux/pfcPHtcfeC5tFJvgK//l0FMhB73mVV5 GOQmrQaqIIcR3v5riiIQyaJ7k8FNUz7HMRvZ8yrAs11gNxpy+7S4fdOCI6aDYlvSVnhK 7vnzZJOjXCDcLq+aNMGeJG7bIXsED/xSkdx3zwMBEeav7fnwr9MnxY5b1vqsBuCsO0as YcIg== X-Gm-Message-State: AN3rC/4Sv8GCCDFyWvktbHmNYdBSrWSgref8w/qcSoZyCTvo0iF1tQNV 3G+x8bmnt6AE3xAwqS4= X-Received: by 10.55.24.155 with SMTP id 27mr25406360qky.161.1493674618148; Mon, 01 May 2017 14:36:58 -0700 (PDT) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com. [209.85.220.172]) by smtp.gmail.com with ESMTPSA id x26sm11950785qtx.69.2017.05.01.14.36.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 May 2017 14:36:57 -0700 (PDT) Received: by mail-qk0-f172.google.com with SMTP id u75so102634875qka.3 for ; Mon, 01 May 2017 14:36:57 -0700 (PDT) X-Received: by 10.55.34.133 with SMTP id i127mr20835953qki.137.1493674616955; Mon, 01 May 2017 14:36:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.135.212 with HTTP; Mon, 1 May 2017 14:36:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 1 May 2017 17:36:56 -0400 X-Gmail-Original-Message-ID: Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1147fe82f42ae1054e7d38d2 Subject: Re: [VOTE] PDO Float Type From: adambaratz@php.net (Adam Baratz) --001a1147fe82f42ae1054e7d38d2 Content-Type: text/plain; charset=UTF-8 Hi, I took another pass at this RFC: *https://wiki.php.net/rfc/pdo_float_type * Most of the discussion in the last round was about fixed precision types. Since there was a lot of disagreement around the right way to handle them, I'd like to keep them out of this RFC. I know Matteo wanted to get them into this RFC, but I'd rather do less if it increases the chances that a group can agree. Nothing in this RFC should interfere with a future implementation of fixed precision types. I added a PR to show how this feature would be implemented. It should make it clear that very little change is needed to open up this functionality. I avoided mixing in type casts or any special formatting to keep things safe and simple. This allowed me to streamline the examples in the RFC quite a bit. It would be helpful to get feedback from anyone who voted "no" previously, but didn't comment in the thread. There's no need to talk through this RFC again if everyone in that group wants fixed precision types to be included. Thanks, Adam --001a1147fe82f42ae1054e7d38d2--