Munge all ErlJSON to use binaries.

Our flavor of ErlJSON has this interesting characteristic:

    {[{foo, bar}]} == {[{<<"foo">>, <<"bar">>}]}

This is fine and dandy for writing ErlJSON that is going to
go directly to a serializer, but when it goes to client code
executing in couch_native_process.erl it becomes a pain in
the but to know whether to use atoms or binaries.

This patch munges all input to user functions to use
binaries except for null, true, and false obviously.

This fixes the commented out test in erlang_views.js as well
as adds a show to poke into the request object that has
known instances of where things get munged.



git-svn-id: https://svn.apache.org/repos/asf/couchdb/trunk@806732 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 0 insertions, 0 deletions

diff --git a/test/run_native_process.es b/test/run_native_process.es
index dfdc423e..dfdc423e 100644..100755
--- a/test/run_native_process.es
+++ b/test/run_native_process.es