vendor/json_pure/CHANGES in scout-5.1.2 vs vendor/json_pure/CHANGES in scout-5.1.3

@@ -1,4 +1,47 @@
[phone] (1.4.2)
+  * Applied patch from naruse Yui NARUSE <[e-mail]> to make building with
+    Microsoft Visual C possible again.
+  * Applied patch from devrandom <[e-mail]> in order to allow building of
+    json_pure if extensiontask is not present.
+  * Thanks to Dustin Schneider <[e-mail]>, who reported a memory
+    leak, which is fixed in this release.
+  * Applied 993f261ccb8f911d2ae57e9db48ec7acd0187283 patch from josh@github.
[phone] (1.4.1)
+  * Fix for a bug reported by Dan DeLeo <[e-mail]>, caused by T_FIXNUM
+    being different on 32bit/64bit architectures.
[phone] (1.4.0)
+  * Major speed improvements and building with simplified
+    directory/file-structure.
+  * Extension should at least be comapatible with MRI, YARV and Rubinius.
[phone] (1.2.4)
+  * Triger const_missing callback to make Rails' dynamic class loading work.
[phone] (1.2.3)
+  * Added a State#[] method which returns an attribute's value in order to
+    increase duck type compatibility to Hash.
[phone] (1.2.2)
+  * Made some changes to make the building of the parser/generator compatible
+    to Rubinius.
[phone] (1.2.1)
+  * Added :symbolize_names option to Parser, which returns symbols instead of
+    strings in object names/keys.
[phone] (1.2.0)
+  * fast_generate now raises an exeception for nan and infinite floats.
+  * On Ruby 1.8 json supports parsing of UTF-8, UTF-16BE, UTF-16LE, UTF-32BE,
+    and UTF-32LE JSON documents now. Under Ruby 1.9 the M17n conversion
+    functions are used to convert from all supported encodings. ASCII-8BIT
+    encoded strings are handled like all strings under Ruby 1.8 were.
+  * Better documentation
[phone] (1.1.9)
+  * Added forgotten main doc file extra_rdoc_files.
[phone] (1.1.8)
+  * Applied a patch by OZAWA Sakuro <[e-mail]> to make json/pure
+    work in environments that don't provide iconv.
+  * Applied patch by okkez_ in order to fix Ruby Bug #1768:
+      http://redmine.ruby-lang.org/issues/show/1768.
+  * Finally got around to avoid the rather paranoid escaping of ?/ characters
+    in the generator's output. The parsers aren't affected by this change.
+    Thanks to Rich Apodaca <[e-mail]> for the suggestion.
 2009-06-29 (1.1.7)
   * Security Fix for JSON::Pure::Parser. A specially designed string could
     cause catastrophic backtracking in one of the parser's regular expressions
     in earlier 1.1.x versions. JSON::Ext::Parser isn't affected by this issue.
     Thanks to Bartosz Blimke <[e-mail]> for reporting this