forward slashes are unnecessarily escaped about json-simple HOT 7 OPEN

Yes, we escape every slash to void issues in HTML (JSON is used in web 
applications
in most cases) and make the code simpler (and slightly efficient and reliable 
code,
without contextual condition handling). Actually JSON.simple focuses on 
supports in
communications between applications (such as web server and browser, distribute
computing), so reliable (100% SPEC compliance and bug free) and efficient are 
two
important consideration, while other features such as pretty printing is not 
supported. 

But I think this is a valid usability concern, so I am setting it as an 
enhancement,
which will be reviewed and may be implemented in the future. 

You are also encouraged to modify and improve the source code directly if you 
need it
right now.

Thanks.

Issue 9 has been merged into this issue.

We use it to encode/decode inter-application (twitter/our app) communication 
which contains quite a few URLs. 
Now to use this library we have to unescape some of the values unnecessarily. I 
do suggest to make this an 
option for the serializer.

[deleted comment]

Issue 77 has been merged into this issue.

I am putting a base64 encoded image into a json object. All the slashes in the 
encoded string are escaped when calling toString(). Thats too bad! Provide a 
toString() and a toEscapedString() method, that the user can choose which one 
to use. :-) 

I have same issue escaping slash. 

Please, provide toString() and toEscapedString() method.