Comments (7)
It may be a convenient extension for some applications but we need to carefully
think
of the following items:
- It's not part of JSON spec (http://www.ietf.org/rfc/rfc4627.txt)
- We have to develop an extension grammar (in BNF or other forms) to JSON spec
and
make compatible to original one
- It may confuse some of users (we have some users who don't like the extension
of
JSON spec in the implementation, see comments on
http://code.google.com/p/json-simple/wiki/DecodingExamples#Notes_-_Multithreadin
g_and_extensions).
So I am a bit reluctant to add this feature.
Original comment by [email protected]
on 17 Mar 2010 at 8:37
from json-simple.
I did notice these discussions earlier. I am definitely sympathetic to both
sides,
although I would find this extension useful. Allow me to ask a few questions
which
might simplify your decisions:
- if I were to provide a patch for this, would you accept it?
- if I were to provide a patch for this and the requested "strict" mode, would
you
accept that?
Original comment by matt.fowles
on 17 Mar 2010 at 3:01
from json-simple.
That will be great!
May I ask what the grammar for the single quoted strings is?
And may I have a look at the codes?
Thanks.
Original comment by [email protected]
on 17 Mar 2010 at 4:16
- Changed state: Accepted
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from json-simple.
The grammar for string would become:
string := double_quote_string | single_quote_string ;
double_quote_string := " double_quote__char* " ;
single_quote_string := ' single_quote_char* ' ;
double_quote_char := any-Unicode-character-except-"-or-\-or-control-character
| \"
| escape_sequence ;
single_quote_char := any-Unicode-character-except-'-or-\-or-control-character
| \'
| escape_sequence ;
escape_sequence := \\ | \/ | \b | \f | \n | \r | \t | \u four-hex-digits ;
I have not written the code yet because I was not sure if you would accept the
patch or
not.
Original comment by matt.fowles
on 17 Mar 2010 at 5:06
from json-simple.
Thanks a lot for providing the grammar. It looks good.
And it seems the changes will have non-trivial impacts on the existing codes.
Could
you provide a sample scenario which requires this enhancement? We need to make
sure
why we need such kind of enhancement.
Thanks.
Original comment by [email protected]
on 18 Mar 2010 at 5:51
from json-simple.
When hardcoding JSON in Java, the string within string issue becomes quite
annoying:
String json = "{ \"asdf\" : \"qwer\\\"zxcv\" }"
vs
String json = "{ 'asdf' : 'qwer\"zxcv' }"
Also, because xml allows either form of quoting for attributes, copying and
pasting
strings from xml requires extra work converting.
Original comment by matt.fowles
on 18 Mar 2010 at 3:03
from json-simple.
I still haven't implemented this because I was waiting on some sort of
indication as to whether or not the code would be accepted. Sorry for the long
delay in response, but life got distracting.
Original comment by matt.fowles
on 8 Jun 2010 at 3:30
from json-simple.
Related Issues (20)
- escaped backslash results in new line character if followed by 'n' or 'r' HOT 1
- JSONParser.parse() throws a parse exception on trailing and leading whitespace of a JSON String. HOT 1
- Make junit's scope to test HOT 3
- Build JSONArray from a Collection HOT 1
- StringBuilder and StringBuffer values are unquoted HOT 1
- I need to modify JSON object value at run time.
- Move project to Github HOT 2
- Migrating to GitHub? HOT 1
- MVN Repo and direct download from https://code.google.com/p/json-simple/ are different jars for the same version 1.1.1
- linkedHashMap does not preserve order once data has reached client
- Please provide a source archive for release 1.1.1
- MAVEN, json-simple 1.1.1 depends on Junit HOT 4
- bug in get(), ContainerFactory HOT 1
- JSONObject produces warning in code HOT 6
- Long cast error, even if String used HOT 2
- Patch for /trunk/src/main/java/org/json/simple/parser/ContainerFactory.java HOT 2
- nothing is being converted to a JSONObject in my java class, throwing an exception HOT 1
- Building 1.1.1 with java-1.8.0 tests fail - hash not matching? HOT 2
- Functions are missing from json_simple.jar (1.1)
- should not always use toString() as fallback in JSONValue.writeJSONString() HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-simple.