Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98304 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11229 invoked from network); 15 Feb 2017 19:02:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Feb 2017 19:02:37 -0000 Authentication-Results: pb1.pair.com header.from=narf@devilix.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=narf@devilix.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.218.42 as permitted sender) X-PHP-List-Original-Sender: narf@devilix.net X-Host-Fingerprint: 209.85.218.42 mail-oi0-f42.google.com Received: from [209.85.218.42] ([209.85.218.42:36622] helo=mail-oi0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 39/21-01562-CC5A4A85 for ; Wed, 15 Feb 2017 14:02:37 -0500 Received: by mail-oi0-f42.google.com with SMTP id u143so91311805oif.3 for ; Wed, 15 Feb 2017 11:02:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devilix.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=delcAg0lxfq4PU5q5DUbv/KAROhqyU509KB+QQuAE0o=; b=hX7taukqhx8l/qCdPKT4eplWfXBdDYifUO9B2eU4Tfz2CfFeyIj4NKZ7Nx59FbWwLZ A6uzOIUOiRDNfWLz9xVhNEp4ElycG0xLt17C3OX4SHWv0Kzgis/CwyqwhgKZxb6jtx+9 Kev1wAZiA8C1KZRwGIWFafcIR/cfRf0F8rOgg= 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:cc; bh=delcAg0lxfq4PU5q5DUbv/KAROhqyU509KB+QQuAE0o=; b=BIU3hBoyAkauRKB84ofNeg+HGqd0jD9wmo6WRpB5CzFluQEx7J6qtFndr9ZPJx75Ob Ha0cIigv0+yB38hZgut5BS0a6lKL+WMZm2rBQdWtg8jdM9ZmfUqY1anVi4NQXUTg+ITW v7LJgm7v2yvlcFx4kDZY8tw7d6a9YXNbjzRdL/l45gLOAoJftfKBKXt/4WuiRDZa22Dw KnZoJteDqsLy5u8n2MCH3Ju8btOAkAewIcLVxlVUZA+xt2G+b3cSUjg9xmo79XICDkfG qMR7LQRtzYbBa/SJndb7OXx9LWPUcPHh19lWpfbrskZ/f4FohCOaPFPf3T/nqbkVG7iI 0Ctg== X-Gm-Message-State: AMke39kbQT0rvtNNYQFfUTiDhv4AAzW2zIKLtF0C53THinbHmL95+HoujPD5xyUU0vpwiPxYzRKwDDgqrlpZDw== X-Received: by 10.202.232.77 with SMTP id f74mr18033415oih.60.1487185354275; Wed, 15 Feb 2017 11:02:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.96.166 with HTTP; Wed, 15 Feb 2017 11:02:33 -0800 (PST) In-Reply-To: References: Date: Wed, 15 Feb 2017 21:02:33 +0200 Message-ID: To: Stanislav Malyshev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1141b0a0c1d46a05489652e7 Subject: Re: [PHP-DEV] [RFC][VOTE] Binary String Deprecation From: narf@devilix.net (Andrey Andreev) --001a1141b0a0c1d46a05489652e7 Content-Type: text/plain; charset=UTF-8 Hi, On Wed, Feb 15, 2017 at 8:35 PM, Stanislav Malyshev wrote: > Hi! > > > 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 > > Same here. I just don't see what is improved by this removal. To me, > it's just disruption (admittedly to a small code base, but still) > without any upside. > > While that's an understandable argument, what happens if we flip it? Is there any benefit to keeping it? If it currently does nothing, and the only reason for keeping it is that it may do something in the future ... Well, there will be side-effects to any code that does use it today. In other words, it's supposed to be providing forward compatibility, but any attempt to actually utilize it may only result in a BC *break*. It's not a function or class name, so nothing benefits from reserving it either ... or am I missing something? Cheers, Andrey. --001a1141b0a0c1d46a05489652e7--