Add Generated JS typedef tests
Add Generated JS tests for enums
Add Generated JS tests for function signatures
Remove old naclbind.js from the prototype
Move genFile function to their own module

This way we can use them for the C generator tests too.

Also remove genText function, and add test/data/simple.h instead.
Rename test/c/{test.cc => main.cc}

This will be used for the C generator tests too.
Change C++ comments to C comments

Also add NB_ONE_FILE guards. These are used when creating one .c file
that includes all of the sources. In that case, we don't want to include
headers (they'll already be in the file).
Pass output file to genFile, not outdir and name

This is more consistent with other functions for compiling, translating,
etc.
Add src/c/run.{c,h}, for running a request

This is the interface we test against for the C Generator tests. An
actual application still needs the PPAPI startup stuff, as well as a
message queue (to push messages to a worker thread).
Add src/c/app.c, remove templates/app.c

This is a very basic app framework. It does only the minimum necessary
to get naclbind working (i.e. no nacl_io, no ppapi_simple).
Add a C generator test

* Modify bin/gen.py to strip comments when including files (this makes
  glue.c easier to read.
* Fix glue.c to use new naclbind C API
* Add test/c/test_gen.js that runs the generator and builds the
  resulting file with the test framework.
* Add test/data/simple.c: this file contains the implementation defined
  in test/data/simple.h. In a real application this would typically be
  implemented in a library.
* Add test/data/test_simple.cc: this is the per-test source file. My
  current thought is that the test_gen.js harness can read the test/data
  directory for test_*.cc files, and build those.
Removing some of the last files from the prototype