RE: [PHP-DEV] [RFC][VOTE] Binary String Deprecation
| From: | Zeev Suraski | Date: | Wed, 15 Feb 2017 12:52:07 +0000 |
| Subject: | RE: [PHP-DEV] [RFC][VOTE] Binary String Deprecation | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-98298@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Dan Ackroyd [mailto:danack@basereality.com]
> Sent: Tuesday, February 14, 2017 8:22 PM
> To: Pedro Magalhães <mail@pmmaga.net>
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC][VOTE] Binary String Deprecation
>
> On 3 February 2017 at 12:47, Pedro Magalhães <mail@pmmaga.net> wrote:
> > Hello internals.
> >
> > After a *very* quiet period of discussion, I have now opened the vote
> > for the Binary String Deprecation.
>
>
> I thought this RFC was likely to pass easily.
>
> It's always slightly unfortunate when RFCs are either accepted or rejected by
> a small margin, particularly when there doesn't seem to have been any
> voices against it.
>
> Please could anyone who voted no, illuminate the rest of us as to why voting
> no was the correct option?
I can't speak for others, but for me, it's simply because there's no reason to do it
(remove it), while there may/might be a reason to keep it going forward. Keeping it comes at zero
cost, and if we ever do need a binary string notation, it sounds more than likely that we'll
pick this one. I see no value at removing it even if there's a small chance we'll need it
again.
I suspect that's why we also saw very little discussion - it's really a non-issue, but it
goes both ways - I probably wouldn't add it if it wasn't in, but I don't see the
logic in removing it now that it's in.
My 2c.
Zeev