1. 11 Feb, 2015 1 commit
  2. 10 Feb, 2015 1 commit
  3. 09 Feb, 2015 5 commits
  4. 04 Feb, 2015 6 commits
    • Wouter van Oortmerssen's avatar
      Clarified how to create a good pull request. · 1fb0f1ef
      Wouter van Oortmerssen authored
      Updated CONTRIBUTING.md with some tips.
      
      Change-Id: Id377621a98804293837fda25ef0758cf988eea37
      1fb0f1ef
    • Alex Ames's avatar
    • Wouter van Oortmerssen's avatar
      Reset minimum alignment when reusing FlatBufferBuilder · 85f64786
      Wouter van Oortmerssen authored
      Previously, if you were re-using instances of FlatBufferBuilder
      and an earlier buffer would use a 64bit item where later ones
      do not, you could be wasting space.
      
      Change-Id: Ic8090a38f97ce73194e991ba72bcfae74a7ace9f
      Tested: on Linux.
      85f64786
    • Florian Enner's avatar
      added reuse option for root objects · b0910e75
      Florian Enner authored
      getRootAs..() function now has a second implementation that
      accepts an existing object to allow object reuse, much like
      all other methods that refer to objects.
      
      Change-Id: Iffef567c903a130761ef7de98867e5465d29a04d
      b0910e75
    • Alex Ames's avatar
      Added new Android build target and makefile utils. · ff1ac8ab
      Alex Ames authored
      Previously Android.mk only had a rule for the Flatbuffers test. There
      is now an empty module definition so that flatbuffers can be included
      as an Android module in other projects.
      
      Additionally, android/jni/include.mk has been added which contains
      some utility functions that can be used by projects using Flatbuffers
      to generate header build rules and set up dependencies.
      
      A sample project has been added to the samples directory to
      demonstrate how to use flatbuffers with Android.
      
      Tested by compiling Android project on Linux.
      
      Change-Id: I25d6da40f6531777b22f7371187e0a2f4e903ad4
      ff1ac8ab
    • pjulien's avatar
      Issue #136 · 4d3db992
      pjulien authored
      The satellite data of the ``ByteBuffer`` cannot be modified in
      any way and stay thread safe in the presence of concurrent readers.
      
      This implementation is simple and does introduce an allocation, however
      without it multiple readers will quickly and continuously encounter
      ``IndexOutOfBoundsException`` exceptions.
      
      An alternative, but possibly more controversial, implementation would
      be to use ``Unsafe``.  Using ``Unsafe``, it's possible to do an
      array copy with a provided buffer index.
      
      Change-Id: I851d4034e753b3be2931ee2249ec2c82dde43135
      4d3db992
  5. 02 Feb, 2015 4 commits
  6. 28 Jan, 2015 1 commit
  7. 26 Jan, 2015 7 commits
  8. 21 Jan, 2015 1 commit
  9. 16 Jan, 2015 5 commits
  10. 08 Jan, 2015 1 commit
  11. 07 Jan, 2015 8 commits