cl-json-devel

cl-json-devel@common-lisp.net

116 discussions

[cl-json-devel] How would you like unlimited hits to your website 15 minutes from now ?
by Hit-Booster＠common-lisp.net 25 Aug '07

25 Aug '07

New Break-through Automation Technology WILL Pull in hordes of Within 15 minutes you will have your own website traffic generator that will bring in an ever increasing amount of hits to your websites! Automatically This software is perfect for bringing real traffic to your site... even if... it's an affiliate link where you have no control over the website content! Using my automated program I have developed, just insert your url... ...choose a category... ...have HIT-BOOSTER send thousands of targeted visitors to your site. Let me tell you what Hit-Booster can do for you ...Hit-Booster will start sending hits to your website instantly at $0 cost to you! ...No matter what you are selling or offering - HIT BOOSTER will pull in hordes of potential customers to your website or affiliate website! ...sets this up completely for you on Auto-Pilot! ...Use it for all of your websites - there is no limit . ...Receive my personal support and email address with your purchase so I can help you to succeed! ...your web site will quickly achieve Ultra High Link Popularity on the Major Search Engines ...you'll get 1000's of Highly Targeted visitors to your web site or affiliate web site overnight ...many are getting more Customers and Sales than they can handle For Full Details please download the attached .html file Unsubscribe Please read the attached .txt file

1 0

[cl-json-devel] How would you like an extra $500 - $1000 a week with 15 minutes of your time ?
by Work＠common-lisp.net 23 Aug '07

23 Aug '07

1 0

[cl-json-devel] Can you afford to lose 300, 000 potential customers per year ?
by Instant＠common-lisp.net 22 Aug '07

22 Aug '07

1 0

[cl-json-devel] Feed Blaster puts your ad right to the screens of millions in 15 Minutes !
by Feed＠common-lisp.net 21 Aug '07

21 Aug '07

1 0

[cl-json-devel] "How would you like to have your ad on 2 Million Websites ?"
by BlogBlaster＠common-lisp.net 20 Aug '07

20 Aug '07

1 0

[cl-json-devel] No Matter what you are selling - Hit-Booster will send targeted visitors to your website!
by Hit-Booster＠common-lisp.net 19 Aug '07

19 Aug '07

1 0

[cl-json-devel] No Matter what you are selling - Hit-Booster will send targeted visitors to your website!
by Hit-Booster＠common-lisp.net 19 Aug '07

19 Aug '07

1 0

[cl-json-devel] How would you like an extra $500 - $1000 a week with 15 minutes of your time ?
by Work＠common-lisp.net 18 Aug '07

18 Aug '07

1 0

[cl-json-devel] Bug with alists
by Slava Akhmechet 30 May '07

30 May '07

I'm running cl-json 0.3.1 and I seem to encounter the following issue on OpenMCL: (encode-json-to-string '(("x" . "blah"))) => "[[\"x\",\"l\",\"a\",\"h\"]]" On SBCL this works as expected: (encode-json-to-string '(("x" . "blah"))) => "{\"x\":\"blah\"}" I could use 'encode-json-alist-to-string', but I'll run into the same problem with inner alist elements of the list (I have an alist of alists). -- Regards, Slava Akhmechet.

1 0

[cl-json-devel] patch to improve encode-json for lists
by Nathan Hawkins 25 Mar '07

25 Mar '07

This fairly simple patch seems to enable encode-json to handle alists. After applying: ;; handles alists (defvar *foo* '((a . 1) (b . 2) (c . 3))) (encode-json-to-string *foo*) --> "{\"a\":1,\"b\":2,\"c\":3}" ;; normal lists still work (defvar *bar* '(1 2 3 4 5)) (encode-json-to-string *bar*) --> "[1,2,3,4,5]" ;; messed up lists of alists which contain lists also works now (defvar *baz* '(((a . 1) (b .2) (c . 3) (d . (1 2 3 4 5))))) (encode-json-to-string *baz*) --> "[{\"a\":1,\"b\":[0.2],\"c\":3,\"d\":[1,2,3,4,5]}]" ;; even better, decode-json likes the output (decode-json-from-string "[{\"a\":1,\"b\":[0.2 ],\"c\":3,\"d\":[1,2,3,4,5]}]") --> (((:A . 1) (:B 0.2) (:C . 3) (:D 1 2 3 4 5))) One thing you can't do is encode a list appended to an alist. That won't work, and I don't know how you'd encode it in JSON anyway. Someone who's had way more sleep than I have lately should test this as well. But I can now both encode and decode lists of alists, which scratches my particular itch... Nathan diff -rN -u old-cl-json/src/encoder.lisp new-cl-json/src/encoder.lisp --- old-cl-json/src/encoder.lisp 2007-03-21 23:29:22.000000000 -0400 +++ new-cl-json/src/encoder.lisp 2007-03-21 23:29:22.000000000 -0400 @@ -25,6 +25,12 @@ (t (write-json-string (funcall *symbol-to-string-fn* s) stream)))) (defmethod encode-json((s sequence ) stream) + (if (and (consp (car s)) + (atom (cdar s))) + (encode-json-alist s stream) + (encode-json-list s stream))) + +(defun encode-json-list (s stream) (let ((first-element t)) (write-char #\[ stream) (map nil #'(lambda (element)

2 2

[cl-json-devel] cl-json asdf packaging.
by Pascal Bourguignon 09 Mar '07

09 Mar '07

There's a problem with the packaging of cl-json. ======================================================================== CL-USER(1): (asdf-install:install :cl-json) ;;; Installing acldns patch, version 1 ;;; ASDF-INSTALL: Downloading 9618 bytes from http://common-lisp.net/project/cl-json/cl-json_0.1.3.tar.gz to /usr/local/asdf-install/site/CL-JSON.asdf-install-tmp ... gpg: Signature made Wed Feb 22 23:15:11 2006 CET using DSA key ID 13DC794B gpg: Can't check signature: public key not found "[GNUPG:] ERRSIG DB0819FF13DC794B 17 2 00 1140646511 9" "[GNUPG:] NO_PUBKEY DB0819FF13DC794B" Error: No key found for key id 0xDB0819FF13DC794B. Try some command like gpg --recv-keys 0xDB0819FF13DC794B [condition type: KEY-NOT-FOUND] Restart actions (select using :continue): 0: Don't check GPG signature for this package 1: Return to Top Level (an "abort" restart). 2: Abort entirely from this (lisp) process. [1] CL-USER(2): :cont 0 ;;; ASDF-INSTALL: Installing /usr/local/asdf-install/site/CL-JSON.asdf-install-tmp in /usr/local/asdf-install/site/, /usr/local/asdf-install/site-systems/ cl-json_0.1.3/src/common.lisp cl-json_0.1.3/src/encoder.lisp cl-json_0.1.3/src/decoder.lisp cl-json_0.1.3/src/package.lisp cl-json_0.1.3/t/testjson.lisp cl-json_0.1.3/t/fail1.json cl-json_0.1.3/t/fail10.json cl-json_0.1.3/t/fail11.json cl-json_0.1.3/t/fail12.json cl-json_0.1.3/t/fail13.json cl-json_0.1.3/t/fail14.json cl-json_0.1.3/t/fail15.json cl-json_0.1.3/t/fail16.json cl-json_0.1.3/t/fail17.json cl-json_0.1.3/t/fail18.json cl-json_0.1.3/t/fail19.json cl-json_0.1.3/t/fail2.json cl-json_0.1.3/t/fail20.json cl-json_0.1.3/t/fail21.json cl-json_0.1.3/t/fail22.json cl-json_0.1.3/t/fail23.json cl-json_0.1.3/t/fail24.json cl-json_0.1.3/t/fail3.json cl-json_0.1.3/t/fail4.json cl-json_0.1.3/t/fail5.json cl-json_0.1.3/t/fail6.json cl-json_0.1.3/t/fail7.json cl-json_0.1.3/t/fail8.json cl-json_0.1.3/t/fail9.json cl-json_0.1.3/t/package.lisp cl-json_0.1.3/t/pass1.json cl-json_0.1.3/t/pass2.json cl-json_0.1.3/t/pass3.json cl-json_0.1.3/t/testencoder.lisp cl-json_0.1.3/t/testdecoder.lisp cl-json_0.1.3/doc/index.html cl-json_0.1.3/doc/style.css cl-json_0.1.3/json.asd #P"/usr/local/asdf-install/site/cl-json_0.1.3/" #P"/usr/local/asdf-install/site/cl-json_0.1.3/" Error: component "cl-json" not found [condition type: MISSING-COMPONENT] Restart actions (select using :continue): 0: Retry installation 1: Return to Top Level (an "abort" restart). 2: Abort entirely from this (lisp) process. [1] CL-USER(3): :cont 1 No man's ambition has a right to stand in the way of performing a simple act of justice. -- John Altgeld CL-USER(4): (asdf:oos 'asdf:load-op :cl-json) Error: component "cl-json" not found [condition type: MISSING-COMPONENT] Restart actions (select using :continue): 0: Return to Top Level (an "abort" restart). 1: Abort entirely from this (lisp) process. [1] CL-USER(5): :q CL-USER(6): ======================================================================== With the attached patch, we can install and load it smoothly. (Rename the system file cl-json.asd and rename the defsystem :cl-json to put some consistency in). ======================================================================== CL-USER(1): (asdf:oos 'asdf:load-op :cl-json) ; loading system definition from ; /usr/local/asdf-install/site-systems/cl-json.asd into ; #<The ASDF0 package> ; registering #<SYSTEM :CL-JSON @ #x71c55e5a> as CL-JSON ; registering #<SYSTEM :JSON.TEST @ #x71aa2b2a> as JSON.TEST NIL ======================================================================== -- Pascal Bourguignon http://www.ravenpack.com/

2 1

[cl-json-devel] Re: cl-json test suite
by Henrik Hjelte 10 Jan '07

10 Jan '07

On Wed, 2007-01-10 at 16:35 +0000, Jonathon McKitrick wrote: > Hi Henrik, > > I'm going to find your cl-json library very helpful! > Wow, a real user! :-) > I have a question about your test suite, as I am also looking into >integrating > a comprehensive test suite to my project. How can you have 2 defsystems in > the same .asd file? How do you load one system and not the other? I don't > think I've ever seen this done before. I'm no expert on asdf, but this works: (asdf:oos 'asdf:load-op :json) followed by (asdf:oos 'asdf:load-op :json.test) I think I saw it in either UnCommonWeb which has a lot of systems in one asd file, or cl-sql, which has an advanced asd file. And please try out the darcs version of cl-json, I have added some stuff like a json-bind macro and json-rpc. There is one thing I want to decide before releasing a new version: I'm not sure that it is the best idea to intern parsed json in the keyword package. Any opinions on this matter or other matters are appreciated.. > I'm trying to decide if my test suite should be a separate system or > integrated into the existing system. Actually when I code most of my things I keep the programmer-tests in the same files and system as the rest of the code. I think tests document and explain how a function is used, and then I don't want to look in another file. Why I keep tests in a separate system for cl-json I don't know, I guess it looks nicer or maybe it is just because I've seen other do this... I can't really think of really why this is better though.. /Henrik

1 0

[cl-json-devel] Characters
by Ken Harris 29 Dec '06

29 Dec '06

Hello! One thing I discovered when I tried to encode a big s-exp with encode-json-to-string is that it doesn't support characters. This kind of makes sense, since JSON itself doesn't have a separate "character" type, and some of the big usrs of JSON (ECMAscript and Python) don't, either. A JSON decoder couldn't tell what's a length-1 string, and what's a character. OTOH, for my program, it would be really handy to *encode* characters directly. I decided to try writing a patch, after about 5 seconds came up with this: (defmethod encode-json ((c character) stream) (encode-json (string c) stream)) Since this is Lisp, it's both insanely easy, and it doesn't have to be part of cl-json for me to use it as if it was. :-) I guess it doesn't really benefit me for this to be part of cl-json, but if that's of any use to you, feel free to use/add it. cheers, - Ken

2 1

[cl-json-devel] (no subject)
by Ben Hyde 31 Oct '06

31 Oct '06

Suggestion: (defun json-escaped-char-to-lisp(json-escaped-char) (or (cdr (assoc json-escaped-char *json-lisp-escaped-chars*)) json-escaped-char)) The existing implementation is correct, just not particularly tolerant of what people actually do. In particular it parsing of json from del.icio.us. It can handle: (json:decode-json-from-string "right's of man") but not (json:decode-json-from-string "right\\'s of man") "generous in what you accept", and all that. - ben "... no code should do that unless it should." -- Marc Slemko

2 2

[cl-json-devel] ANN: cl-json 0.1.3
by Henrik Hjelte 22 Feb '06

22 Feb '06

is available by asdf-install. Contains a bugfix when encoding hash-tables. /Henrik Hjelte

1 0

[cl-json-devel] Escaping of symbols in hash tables
by Richard Newman 22 Feb '06

22 Feb '06

Hi, Is this intentional? (This tested against a brand-new checkout from the darcs repo.) ---- * (in-package :json) #<PACKAGE "JSON"> * (encode-json-to-string 'x) "\"X\"" * (make-hash-table) #<HASH-TABLE :TEST EQL :COUNT 0 {40148169}> * (setf (gethash 'x *) 5) 5 * (encode-json-to-string **) "{\"\"X\"\":5}" ---- Dump this out to a stream, and you get {""X"":5} which isn't so useful. I suspect it's because the symbol is encoded to "X", and then wrapped in quotes anyway. I thought I'd mail the list before attempting to fix and submit a patch. Opinions? -R

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

cl-json-devel