Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix too many recursiver errors on deeply nested alist structures #5

Merged
merged 1 commit into from Nov 7, 2014

Conversation

bobbysmith007
Copy link
Contributor

This case was crashing threads in modern sbcl, if the json was
large due to exceeding the maximum error depth

(json:encode-json-alist-to-string
(json:decode-json-from-string json))

  • Replace direct call in the error handler with restart invokation
  • fix bug where if the value of an alist-cell was an alist we wouldnt
    try parsing it as one (the cdr was a cons)
  • use symbol names for list encoder so that changes in the encoder
    (such as tracing adding break points) show up without having to
    switch that variable

This fixes issue:1

This case was crashing threads in modern sbcl, if the json was
large due to exceeding the maximum error depth

  (json:encode-json-alist-to-string
     (json:decode-json-from-string *json*))

 * Replace direct call in the error handler with restart invokation
 * fix bug where if the value of an alist-cell was an alist we wouldnt
   try parsing it as one (the cdr was a cons)
 * use symbol names for list encoder so that changes in the encoder
   (such as tracing adding break points) show up without having to
   switch that variable
@bobbysmith007 bobbysmith007 mentioned this pull request May 7, 2014
hankhero added a commit that referenced this pull request Nov 7, 2014
Fix too many recursiver errors on deeply nested alist structures
@hankhero hankhero merged commit 37c3c70 into hankhero:master Nov 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants