json at Yahoo! Groups

Using ACLs in JSON

Peter brooks — Tue, 21 May 2013 14:07:38 GMT

I'm designing a system that should allow different views to different audiences. I understand that I can use application logic to control the access security,

Corn-Converter

Serhat — Sun, 19 May 2013 21:22:36 GMT

Corn-Converter (website: https://sites.google.com/site/javacornproject/corn-converter) is small, fast and extensible JSON converter that written in java is

Re: Introducing NXJSON parser (written in C)

wjosdejong — Tue, 14 May 2013 07:01:25 GMT

Though very practical and desired by many, comments are not supported by JSON. To prevent compatibility issues in the future, it may be better to be consistent

Introducing NXJSON parser (written in C)

yarosla — Mon, 13 May 2013 21:32:41 GMT

NXJSON is full-featured yet very small (~400 lines of code) JSON parser, which has easy to use API. Features Parses JSON from null-terminated string Easy to

New JSON decoder for Fortran

spineynorton — Mon, 13 May 2013 16:55:47 GMT

I've just released a JSON decoder for Fortran that is built on top of YAJL. The YAJL-Fort project page is http://sourceforge.net/projects/yajl-fort/ It looks

New JSON decoder

Jonas T?rnstr?m — Fri, 26 Apr 2013 14:04:34 GMT

Hi, We?ve released the ujson4c decoder, based on UltraJSON to which it adds a more painless API for robust and performant day to day C/C++ JSON decoding

Update to JSON APIs available for LabVIEW

labviewhacker — Fri, 26 Apr 2013 12:20:13 GMT

Hi Douglas and fellow JSON-lovers, Thank you for posting the JSON API I made for LabVIEW last year on JSON.org. I wanted to fix the name of the toolkit as

New version and URL for Lua module dkjson

David Heiko Kolf — Sun, 14 Apr 2013 19:57:16 GMT

Hello, I have released new versions of my Lua module dkjson and changed the URL. The new URL would be and I was told

Re: JSON strings cannot point to post-BMP Unicode codepoints?

Shriramana Sharma — Mon, 08 Apr 2013 13:51:43 GMT

Hello people and thanks for your responses. I hope I understand correctly that compatibility with JavaScript and the ECMAScript standard dictates that it would

Re: JSON strings cannot point to post-BMP Unicode codepoints?

John Cowan — Mon, 08 Apr 2013 09:11:29 GMT

... That's right. However, escapes are handy for representing stray Unicode characters that aren't easy to type, just as in HTML or XML. Unlike those

Re: JSON strings cannot point to post-BMP Unicode codepoints?

Dennis Gearon — Mon, 08 Apr 2013 04:41:49 GMT

There's some contradiction in the json RFC. If the encoding 'shall be Unicode' and default is UTF-8 as is stated, then ALL normal planes, including those

Re: JSON strings cannot point to post-BMP Unicode codepoints?

douglascrockford — Sun, 07 Apr 2013 18:30:28 GMT

JavaScript, Java, and many other languages, were developed at a time when Unicode was going to be a 16-bit character set. Unicode later grew into a 21-bit

Re: JSON strings cannot point to post-BMP Unicode codepoints?

John Cowan — Sun, 07 Apr 2013 18:21:46 GMT

... It can be represented either as the actual character, 4 bytes in any of UTF-8, UTF-16, or UTF-32; or else as two consecutive ASCII escapes: "\uD804\uDC05".

Re: JSON strings cannot point to post-BMP Unicode codepoints?

David Heiko Kolf — Sun, 07 Apr 2013 17:53:00 GMT

... Yes, you can put post-BMP codepoints directly as part of the string literals. If there are control characters outside of the BMP in your text they could

Re: JSON strings cannot point to post-BMP Unicode codepoints?

douglascrockford — Sun, 07 Apr 2013 17:45:58 GMT

From RFC 4672 http://www.ietf.org/rfc/rfc4627.txt?number=4627 To escape an extended character that is not in the Basic Multilingual Plane, the character is