Closed ashb closed 12 years ago
Loading json/pure.rb directly causes it to issue redefined warnings under a Rails app.
json.rb (as found in json_pure) will first try to load json/ext and if that fails falls back to json/pure, so this is better all round (faster, works.)
Fixed in commit: 41c11d528f and deployed in gem version 1.4.0
Loading json/pure.rb directly causes it to issue redefined warnings under a Rails app.
json.rb (as found in json_pure) will first try to load json/ext and if that fails falls back to json/pure, so this is better all round (faster, works.)