Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98931
Return-Path: <narf@devilix.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 33834 invoked from network); 2 May 2017 10:56:49 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 2 May 2017 10:56:49 -0000
Authentication-Results: pb1.pair.com smtp.mail=narf@devilix.net; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=narf@devilix.net; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.214.54 as permitted sender)
X-PHP-List-Original-Sender: narf@devilix.net
X-Host-Fingerprint: 209.85.214.54 mail-it0-f54.google.com  
Received: from [209.85.214.54] ([209.85.214.54:36542] helo=mail-it0-f54.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id D5/34-02776-0F568095 for <internals@lists.php.net>; Tue, 02 May 2017 06:56:48 -0400
Received: by mail-it0-f54.google.com with SMTP id o5so293107ith.1
        for <internals@lists.php.net>; Tue, 02 May 2017 03:56:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=devilix.net; s=google;
        h=mime-version:from:date:message-id:subject:to;
        bh=opdVgZj8p1VAB1MSLfMcoRjoFLU9PG60wcNmlN8LUTs=;
        b=m1JX7QkuiNGcWaAPa7Y9339p/AiUoumpzsSn+YwlTDkMT3ahldQpIWKv6V3CA2w/rF
         WwuxgsMC9vKUhZ2qpC35gVOHopwTkz8CMytybmZbJ1cRgK+PoLlwxFC7VB48dbrCuz9o
         4/EsFDFtn9QgDJa2/eL2bqyx3dis+W35rIMEw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=opdVgZj8p1VAB1MSLfMcoRjoFLU9PG60wcNmlN8LUTs=;
        b=M9nNrmmzTp8fJnpCcKsvLqQftE9wvou+vZDRFbZnPZLzk3mQtPfnOWwjw2gvhueSWt
         jq2lj5cNdu/rxXT/XJLM2CSZo+V+ijQKQlrUIpJESLrK4OGy0prkbAuVmVI53TqyR/KK
         en0o09/8au9g13yWPH/kNhbHcw7Nk9XCBg+1tBTdEC7lXqX2Vlo4MzenmRrlXrMGZDYL
         eZl7N741lBx8ZZ/rTZnE/VP66HV6l401q5fHyg/kVCoA8EbqT/Swfa5nlFvWn2jsKqJi
         xgeN5e3Hub7pXBtnlEZbY1y3BId56Xb8YQwiW/qZzh8KdDssmzvt3P9qfSpIs4Z3GvYw
         T/JQ==
X-Gm-Message-State: AN3rC/7RS8gnbfFGH67K6kRSQ5p3+25XQy0YMFTFoQ1RbyMJcxJr5Py2
	bnN7E6JuBHzeo+Qgktvmj3dtWvhhipOY8As=
X-Received: by 10.202.226.75 with SMTP id z72mr4780877oig.142.1493722605495;
 Tue, 02 May 2017 03:56:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.110.7 with HTTP; Tue, 2 May 2017 03:56:45 -0700 (PDT)
Date: Tue, 2 May 2017 13:56:45 +0300
Message-ID: <CAPhkiZzzgmWcqsVPKghv89XU3+Ab06wcXbqeBc1MSh401_+etw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: [Discussion] Dots and spaces in GPC variable names
From: narf@devilix.net (Andrey Andreev)

Hi all,

With parse_str() usage without a second parameter being deprecated, I
was looking to possibly drop the behavior where it replaces spaces and
dots with underscores in the result array, and ... As it often turns
out - it's not that simple, because it re-uses the code that handles
GPC vars.

I didn't even know this mangling happened with GPC vars. I can only
assume that's legacy from the the register_global days, as I certainly
don't see a reason for it now. Am I missing something?

And more importantly, can we change that? It's a significant BC break,
yes, but the current behavior is horribly broken IMO.

Cheers,
Andrey.