Change-Id: I7c04d934bfacd4aeaa2ba476b934dd3a62d4fc0e
Tested: on Linux.

Change-Id: Ie19af91ec5bf0b65297cba58c124bceaa58fd73e

Because they are represented as `const T *` in the Vector template,
the sizeof(const T *) was accidentally used instead of sizeof(T).

Change-Id: Ib4dc73e1d21396ba2e30c84e5e229c4147204bb1
Tested: on Linux.

Add support for JavaScript code generation with Google Closure Compiler type annotations

Ported some of the python fuzz tests to C#

Fix minor typos in the Python documentation.

* Refactored the test runner to use attribute based test discovery
* Ported value and vtable/object fuzzing tests from python to C#

This adds an optional argument to generated getters for string fields to
specify the encoding type and overloads the createString() function. It's
now possible to use either JavaScript UTF-16 string objects or C-style
UTF-8 byte arrays (Uint8Array) for string data.

JavaScript uses UTF-16 but FlatBuffers uses UTF-8. This commit tests the code
that does the conversion between the two encodings. The last entry in the array
is tricky because each code point actually requires two UTF-16 code units,
unlike the other examples. The current JSON output of flatc actually handles
this case incorrectly (it generates invalid JSON with UTF-8 code units). The
generated JavaScript code passes these tests fine, however.

This adds a JavaScript language target. The generated JavaScript uses Google
Closure Compiler type annotations and can be compiled using the advanced
compilation mode, which performs type checking and optimizations such as
inlining and dead code elimination. The generated JavaScript also exports all
generated symbols for use with Node.js and RequireJS. This export behavior
can be turned off with the --no-js-exports flag for use with Google Closure
Compiler.

Change-Id: I6600021b7ec8c486794349511232c3e604421c5b
Tested: on Linux.

Add self.assertNotNested() in CreateString

And also add a test case.
If you try to nest CreateString you will get a clear exception.

Change-Id: I62de6b7008e397a5043d47f014a7acd83ee64740

Bug: 24401812
Change-Id: I196a03b8c5ef0bcd3c26178239c764e40ca1950d
Tested: on Linux.

Fix 32bit-system integer overflow (test only)

For #277

Removed call to pop_back on std::string.

Change-Id: If414d156b4e9bc7fead5f131823b2c419cdc4e2c
Tested: on Linux.

The pop_back function was added to strings in C++11 and it appears not
all compilers we target support it. The call to pop_back has been
replaced with a call to erase.

Tested on Linux. All unit tests pass.

Fix an out-of bounds read when the element is bigger than the buffer.

Remove duplicate Go test

Ensure the size of the buffer being checked is bigger than the element
of the buffer being checked. The buffer can be triggered when, for
example, the buffer is of length zero and we are checking for:

    Verify<uoffset_t>(buf_)

The condition above should fail.

Change-Id: I90cf519c00eaf9ccd9fcab8035a91b9205587c3b

Implemented option --scoped-enum for C++ generator

This generates C++11 style scoped and strongly typed enums.
Enabling this option also implies --no-prefix.

Fix before_install step on .travis.yml file for osx

Change-Id: I9654e0c6a45457c8e150f07dd5f7b39539266f9e

Also, remove execute permissions on several source files.

Tested: Builds on Visual Studio 2012, and Linux.

Change-Id: Idaacb2ae8eba98ce2974218c2ab840e97a1d67e9

Add @SuppressWarnings("all") to generated Java classes

Usually generators add @SuppressWarnings("all") to generated Java
classes to prevent IDEs from complaining about unused imports, etc.
Solving used imports seems pretty hard with current generator logic so
IMO this is the next best thing.

Yes, it’s appended to import block but that is the block that gives
these warnings in the first place.