Mark W. wrote:
I would follow my nose in search of headers and examine the makefile.
Despite ruby gems, I find using my operating systems package management
usually
works best. I also prefer pure ruby implementations where possible,
because
it’s
less bugger (for me) to fetch via gem. And if I was worried about
performance
I’d have waited for skipped ‘scripting’ languages…
Terry@Dixie$ gem search json -b
4:51
*** LOCAL GEMS ***
*** REMOTE GEMS ***
Bulk updating Gem source index for: http://gems.rubyforge.org
fjson (0.1.2, 0.1.1, 0.1.0, 0.0.9, 0.0.8, 0.0.7, 0.0.6, 0.0.5, 0.0.4,
0.0.3,
0.0.2, 0.0.1)
This library is for parsing JSON strings and unparsing ruby data
structures. This library is a fork of Florian F.'s JSON library
with key parts implemented in C for performance improvements.
json (1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 0.4.3, 0.4.2,
0.4.1,
0.4.0)
A JSON implementation as a Ruby extension
json_pure (1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0)
A JSON implementation in Ruby
Orbjson (0.0.4, 0.0.3, 0.0.2, 0.0.1)
Lib for creating JSON-RPC server applications.
ruby-json (1.1.2, 1.1.1)
ruby-json is a library for using JavaScript Object Notation (JSON)
under Ruby.
Terry@Dixie$
4:52