On 21 Oct 2013, at 21:33, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
What would be the possible steps?
There are 23 implementors and 56 senders of #leadingChar ;-)
Stef
On Oct 21, 2013, at 9:26 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Phil,
On 21 Oct 2013, at 21:09, "phil@highoctane.be" <phil@highoctane.be> wrote:
Well, for one, removing leadingChar will make the urlEncode/urlDecode work properly for the test, as now, the leadingChar thing prevents it.
Read my last comment in https://pharo.fogbugz.com/f/cases/6368/deprecate-unescapePercents-and-encode...
I rewrote the test without the language environment stuff, it should pass.
As it is now, leadingChar generates a code point outside of the unicode range, making leadingChar a non supportable element.
Let's get that out.
Yes, longer term I think we should indeed remove it.
Phil
Sven