Wow.  That's the first time I've gotten a response from a mailing list by
merely googling for an answer--and faster than sometimes when I've asked
directly, too.  Impressive. :)

I was enjoying messing around with PicoLisp, and wanted to know what the
library situation looked like for some key modules before I dove in.  I
found your post about processing PicoLisp client-side rather than working
with JSON server-side, and the one where you wrote that you gave up, and
were going to shell out to Ruby for HTML escapes.  An interesting

Thanks very much for the encoder.  I haven't written anything meaningful in
PicoLisp yet (I only even worked through the tutorial yesterday), but am
going to try to write something simple sometime this week.  Having
server-side JSON support is going to make what I have in mind vastly
simpler.  PicoLisp looks fascinating; this should be quite fun.


On Mon, Dec 14, 2009 at 5:12 AM, Henrik Sarvell <> wrote:

> I just noticed that someone had searched for "picolisp json" on
> Google, I've attached the JSON encoder/decoder to this mail.
> However there is one problem, it isn't properly managing when there
> are complex texts involved, then the double quote escaping might get
> it wrong if there are already escaped double quotes in the text and so
> on. That's what I suspect anyway, I was too lazy to properly debug
> when I ran into problems, both because debugging decoding failures on
> the JS side is extremely tedious and because the size of the text that
> was failing was enormous.
> Possibly outdated documentation here:
> (should be
> better than nothing though).
> /Henrik

Reply via email to