yajl-ffi 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +4 -5
- data/lib/yajl/ffi/version.rb +1 -1
- data/lib/yajl/ffi.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 91b3e4f40a342d0b737483a32c14789d13901071
|
4
|
+
data.tar.gz: acfebb0bf6867ee99cc39f44411b394dd697acbf
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 4894734f7816e431e19f05e81ddbc30e5e30aa79d1712d421af4f24f2b377b8868b4e1ff5324ff6a0bf49bceafd5cc79675ed495eaa63700502cbd1dcbb45e9e
|
7
|
+
data.tar.gz: 7dcc45a9609c6f9f99ff3db4fbdaa86e97e6a96ef247b7347dc418c56ba241f33e2a7a2848205b55db743f4bc5a4271da84189418e8d3cbb00200a4564facecf
|
data/README.md
CHANGED
@@ -23,11 +23,10 @@ obj = Yajl::FFI::Parser.parse(json)
|
|
23
23
|
```
|
24
24
|
|
25
25
|
While it's possible to do this with Yajl::FFI, we should really use the
|
26
|
-
standard library's [json](
|
27
|
-
|
28
|
-
|
29
|
-
|
30
|
-
formed.
|
26
|
+
standard library's [json](https://github.com/flori/json) gem for documents
|
27
|
+
like this. It's faster because it doesn't need to generate events and notify
|
28
|
+
observers each time the parser changes state. It parses and builds the Ruby
|
29
|
+
object entirely in native code and hands it back to us, fully formed.
|
31
30
|
|
32
31
|
For larger documents, we can use an IO object to stream it into the parser.
|
33
32
|
We still need room for the parsed object, but the document itself is never
|
data/lib/yajl/ffi/version.rb
CHANGED
data/lib/yajl/ffi.rb
CHANGED