joaorobertoct2 / x-superobject

Automatically exported from code.google.com/p/x-superobject
0 stars 0 forks source link

Cannot Parse data that has #10 and/or #10 #62

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Create Json String with a named value "NAME":"VALUE" where "VALUE" has #10 or 
#13
2.Try and load Json string to TSuperObject
3.

What is the expected output? What do you see instead?
Named object should retain #10 and #13 characters

What version of the product are you using? On what operating system?
R86

Please provide any additional information below.
Changed XSuperJson at lines 960,965
Removed $10 and #13 from RString.add 
Removed $10 and #13 from RString2.add 

//  rString.Add(optAll - ['"', #0, #10, #13], TUseRouteTrigger.Create(rString, 
[], ppNil));
  rString.Add(optAll - ['"', #0], TUseRouteTrigger.Create(rString, [], ppNil));

//  rString2.Add(optAll - ['''', #0, #10, #13], 
TUseRouteTrigger.Create(rString2, [], ppNil));
  rString2.Add(optAll - ['''', #0], TUseRouteTrigger.Create(rString2, [], ppNil));

Some of our clients do not escape the #10 #13 characters and this worked fine 
in the old SuperObject.

Original issue reported on code.google.com by b...@percontidatasystems.com on 24 Feb 2015 at 9:21

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r89.

Original comment by onryld...@gmail.com on 10 Mar 2015 at 10:20