1. 18 Nov, 2012 2 commits
  2. 12 Nov, 2012 1 commit
  3. 04 Nov, 2012 2 commits
    • remove-read-from-string-from-parse-number · 63f7a7e8
      Ignore-this: 61d7e8213b5e0fc764ebfbe7cc199c66
      PARSE-NUMBER used to use READ-FROM-STRING.  This was causing problems with
      some application-building systems. We replace use of the reader (through
      read-from-string) by PARSE-NUMBER.
      rpgoldman authored
    • fix-fiveam-test-comparisons · 670edc27
      Ignore-this: 7fb473839da0e7ffbf84b6b4088cb91c
      FiveAM would like the expected value to be before the computed value, for
      best printing when tests fail.  I reversed the arguments to the
      JSON-NUMBER test to agree with this convention.
      rpgoldman authored
  4. 15 Oct, 2012 3 commits
  5. 14 Oct, 2012 1 commit
    • fix-test-after-method-bug-from-juanjo · d6e60df7
      Ignore-this: 12cec5052070f37a2f72e4e5b0587c32
      juanjo (Juan Jose Garcia-Ripoli) found a bug in the binding of the
      *JSON-TEST-FILES-PATH* global.  Fixed by moving the initializer into
      the test code, and using the ASDF:SYSTEM-RELATIVE-PATHNAME function.
      At the same time, killed the testjson.lisp file, which does the testing
      as a side-effect of loading.  This is unnecessary because the testing
      is done in the PERFORM method of the TEST-OP.
      rpgoldman authored
  6. 13 Jun, 2011 1 commit
  7. 25 Jun, 2011 4 commits
  8. 24 Jun, 2011 1 commit
  9. 23 Jun, 2011 3 commits
  10. 22 Jun, 2011 1 commit
  11. 15 Jan, 2010 1 commit
  12. 14 Jan, 2010 2 commits
    • add-json-rpc-2.0-support · e1121307
      A large number of changes that provide json-rpc-2.0 support to
      cl-json.  Tests are included.
      rpgoldman authored
    • record-function-names-not-functions · b21341a9
        Originally, when one defined a function to be exported as a json-rpc
        function, the function object was cached in a hash table.  This made it
        very difficult to debug with the CL tracer, since the trace-encapsulated
        function wouldn't make it onto the function table.  However, this problem
        goes away with this patch, which caches the function /name/ (a symbol)
        instead of the function itself.  Since json-rpc functions are invoked
        with APPLY, nothing else need change.  Slightly less efficient, but
        JSON-RPC is never going to be that efficient anyway.
      rpgoldman authored
  13. 13 Jan, 2010 1 commit
  14. 10 Jan, 2010 2 commits
  15. 05 Jan, 2010 1 commit
    • catch-read-numeric-overflow-on-allegro · 34680276
      On Allegro Common Lisp, when there's a numeric overflow in the reader,
      they don't signal a reader-error, but a simple-error (I have reported this
      and they may fix it in the future).  This patch makes use of information
      about that simple-error to catch the case in parse-number and treat it
      the way parse-number overflows are handled on other lisps.
      rpgoldman authored
  16. 02 Jan, 2010 1 commit
    • removed-allegro-from-some-tests · 8ccdfebc
      Some tests don't work on allegro on macosx or on allegro simpliciter.
      These seem like limitations of allegro, so I have added features flags
      to mask them.
      rpgoldman authored
  17. 30 Dec, 2009 1 commit
    • json-rpc-handle-notifications · 7a362e8b
      A couple of modifications to hande JSON-RPC notifications (like normal requests, but they
      don't expect a response).
      Also made it possible to invoke a helper function of invoke-json with the pieces of the
      request.  This is necessary because you can't use the standard invoke-rpc if you've
      already parsed the JSON message from the client.
      rpgoldman authored
  18. 06 Jan, 2010 3 commits
  19. 02 Jan, 2010 3 commits
    • trap-acl-overflow-on-read · 86221e84
      Allegro just raises a simple-error when it reads a floating point
      number that's too big.  So we have to catch simple errors when
      in parse-number on allegro.
      rpgoldman authored
    • revise json file loading for tests · a72bac35
      With asdf-binary-locations on, as it will be in new versions of ASDF,
      it is no longer possible to use load-pathname or load-truename to find
      files from loaded binaries.  In the general case, binaries may not be
      located in the same directory as the source files from which they are
      We avoid this problem by caching the value of *load-truename* inside
      code that is run in the .asd file, and then referring to it later on.
      The *load-truename* of the .asd file will remain constant.
      rpgoldman authored
    • add test op to cl-json · a11743f4
      Made it easier to test cl-json by adding an asdf test-op to the asdf
      system definition, and providing a PERFORM method for it.
      Now one can simply say (asdf:oos 'asdf:test-op :cl-json) to load
      the system and run the FiveAM based tests.
      rpgoldman authored
  20. 02 Dec, 2009 2 commits
  21. 12 Oct, 2009 1 commit
  22. 09 Oct, 2009 3 commits