Languages of the real and artificial - Latest Comments in Readable JavaScript Values

Re: Readable JavaScript Values

Vijay Santhanam — Thu, 27 Sep 2007 09:11:21 -0000

I think your constructor checks in Readable.toReadable(value,options) for Regexp, String etc should also include Date to use the native toString() date stringifier.

Re: Readable JavaScript Values

Vijay Santhanam — Thu, 20 Sep 2007 13:25:42 -0000

Nope, not sure what i was witnessing, but new String(value) is wrong too. String(value) is now working for me. Readable.toReadable(null) returns a string now

Re: Readable JavaScript Values

Vijay Santhanam — Thu, 20 Sep 2007 13:11:49 -0000

Thanks Oliver. This is very handy.

I'm starting to code thicker clients with javascript and I've been looking for cool debugging tools like this.

Is it okay if I try merging this with jquery.debug?
http://jquery.glyphix.com/

Also, I believe the first check for null and undefined in Readable.toReadable(value,options) should return a "new String(value)" and not "String(value)".

Re: Readable JavaScript Values

Rick Thomas — Wed, 24 May 2006 23:58:23 -0000

Thanks, Oliver.
This is a much needed tool that saved the day today and I'm sure on many future days.
Good work! Now to spread the word.

Re: Readable JavaScript Values

osteele — Wed, 08 Mar 2006 21:09:06 -0000

Good question. In brief, JSON output is intended for consumption by computers and by libraries written in other languages, and Readable output is intended for humans. This has all sorts of repercussions such as whether RegExps, null, undefined, and NaN are represented; whether representations can be limited in length or depth, and so on. For a longer answer, see the bottom of the docs http://osteele.com/sources/..., where I've just added a list of differences.

Re: Readable JavaScript Values

Asger Ottar Alstrup — Wed, 08 Mar 2006 07:22:14 -0000

How does this compare to JSON?