Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46915
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.218 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=YhgAJfOQlBP+bBN1Lmr8rnhFD+PEPKs+OAsAq9tGnxm/Ws15LdAgpetSGCOCgjg2Yq
         OSx1o9uBKbjq01EyJpqn3HY8F0eeN0gRup169bxtSMiiFiqm3uyV7+u9szl9pCgWkfNj
         1Kf4st25lKzD9EtUZ5Ev2FoUxgBfBoPgt9U/U=
Message-ID: <4B65AB73.9020503@gmail.com>
Date: Sun, 31 Jan 2010 16:10:27 +0000
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Richard Lynch <ceo@l-i-e.com>
CC: Dave Ingram <dave@dmi.me.uk>, internals@lists.php.net
References: <F5.B2.11262.189775B4@pb1.pair.com>    <3392.98.193.1264087265.squirrel@www.l-i-e.com>    <4B58805C.8060004@dmi.me.uk> <3344.98.193.1264918302.squirrel@www.l-i-e.com>
In-Reply-To: <3344.98.193.1264918302.squirrel@www.l-i-e.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Dots and spaces in variable names are converted to
   underscores.
From: nrixham@gmail.com (Nathan Rixham)

Richard Lynch wrote:
> I have taken the liberty of making an RFC for this:
> http://wiki.php.net/rfc/url_dots
> 
> Feel free to add/edit it as fit, particularly since it's my first use
> of that RFC wiki, and I'm not good at wiki markup, and I probably
> missed something from this thread.
> 
> I intentionally left out the ?a_b=1&a.b=2 because that seemed to me to
> be beyond the scope, since ?a_b=1&a_b=2 is equally problematic in
> PHP...
> 
> That said, I am now leaning towards not trying to be BC, and just
> dropping 'a_b' entirely.
> 
> It seems unlikely that anybody doing anything "sane" to attempt to
> reconstruct their original keys is going to be hurt by PHP not messing
> them up anymore.
> 
> Most likely, their revisionary code is simply not going to find any
> 'a_b' to blindly revert to 'a.b' anymore, and the 'a.b' is going to
> just sail through.
> 
> Of course, their a.b might be a^b or a*b or whatever, but whatever it
> is, PHP not messing it up will just mean their code won't find
> anything to "un-do" any more.
> 
> I did think of one other issue though:
> 
> There may be some really funky character that is valid in the URL, but
> that is not kosher for an array/hash key which is currently being
> masked...
> 
> It would still have to be masked if such a character exists...
> 
> I can't think of any such character, but what with i18n of DNS records
> and whatnot these days, I am woefully ignorant of what might be in the
> keys.
> 
> I put that into the RFC already.
> 

Thanks Richard,

I was struggling to get to time to write this up - all seems fine to me
and just as discussed on-list.

Thanks again,

Nathan