> On 18 Jan 2017, at 16:38, Sven Van Caekenberghe wrote:
>
> So my conclusion would be (while writing), always escape $\ and not $/, in
> pure STON mode (the default), escape $' and not $", in JSON mode, escape $"
> and not $'.
I implemented these changes in writing behaviour:
===
Name: STO
On Wed, Jan 18, 2017 at 04:38:15PM +0100, Sven Van Caekenberghe wrote:
> Being a superset means that you get a simple JSON parser (and even limited
> writer) for free once you install STON (or once it is part of the Pharo
> image, as it is now). It also means that we can fall back to the JSON spe
> On 18 Jan 2017, at 16:20, Peter Uhnak wrote:
>
> On Wed, Jan 18, 2017 at 03:38:17PM +0100, Sven Van Caekenberghe wrote:
>> So talking only about the encoding/writing phase, the conclusion would be
>
> 10. Generators
>
> A JSON generator produces JSON text. The resulting text MUST
> st
On Wed, Jan 18, 2017 at 03:38:17PM +0100, Sven Van Caekenberghe wrote:
> So talking only about the encoding/writing phase, the conclusion would be
10. Generators
A JSON generator produces JSON text. The resulting text MUST
strictly conform to the JSON grammar.
I guess the ABNF table is
So talking only about the encoding/writing phase, the conclusion would be
- not to escape $/
- escape everything with code points [0,31], using named escapes if they
exist, else \u
- escape $\ itself
That leaves the question about $' and $".
$' is used in STON as string delimiter, so i
On Wed, Jan 18, 2017 at 11:11:06AM +0100, Christophe Demarey wrote:
>
> > Le 18 janv. 2017 à 09:51, Sven Van Caekenberghe a écrit :
> >
> > Hi Christophe,
> >
> >> STON toString: 'g...@github.com:foo/bar.git’ =>
> >> ''g...@github.com:foo\/bar.git’'
> >> It used to be ''g...@github.com:foo/bar
> Le 18 janv. 2017 à 09:51, Sven Van Caekenberghe a écrit :
>
> Hi Christophe,
>
>> On 18 Jan 2017, at 09:30, Christophe Demarey
>> wrote:
>>
>> Hi,
>>
>> I just noticed that STON encoding of forward slashes changed.
>>
>> STON toString: 'g...@github.com:foo/bar.git’ =>
>> ''g...@github.c
Hi Christophe,
> On 18 Jan 2017, at 09:30, Christophe Demarey
> wrote:
>
> Hi,
>
> I just noticed that STON encoding of forward slashes changed.
>
> STON toString: 'g...@github.com:foo/bar.git’ =>
> ''g...@github.com:foo\/bar.git’'
>
> It used to be ''g...@github.com:foo/bar.git’’.
>
> Is
Hi,
I just noticed that STON encoding of forward slashes changed.
STON toString: 'g...@github.com:foo/bar.git’ => ''g...@github.com:foo\/bar.git’'
It used to be ''g...@github.com:foo/bar.git’’.
Is it on purpose?
Thanks,
Christophe
