Re: [json] Re: Universal Binary JSON Specification
- Patrick Maupin scripsit:
> In terms of design features, have you looked at the PythonUnfortunately, the various pickle formats are apparently not documented
> pickle/cPickle modules? Even though the problem you are solving is
> not exactly the same as the problem those solve, the problems are
> quite similar, and it may be instructive to examine a data format that
> solves a similar problem, and the well-tested underlying code (both
> pure Python and C available) that implements readers and writers for
> the format.
anywhere that Google can find. Can you provide a pointer?
format 0, the textual representation, as you'd expect.)
John Cowan cowan@... http://ccil.org/~cowan
Any sufficiently-complicated C or Fortran program contains an ad-hoc,
informally-specified bug-ridden slow implementation of half of Common Lisp.
--Greenspun's Tenth Rule of Programming (rules 1-9 are unknown)
- On Mon, Feb 20, 2012 at 9:42 AM, rkalla123 <rkalla@...> wrote:
> Stephan,For what it is worth, I also consider support for only signed values a
> No problem; your feedback are still very applicable and much appreciated.
> The additional view-point on the signed/unsigned issue was exactly what I was hoping for. My primary goal has always been simplicity and I know at least from the Java world, going with unsigned values would have made the impl distinctly *not* simple (and an annoying API).
> So I am glad to get some validation there that I am not alienating every other language at the cost of Java.
-+ Tatu +-