1. 22 Mar, 2014 3 commits
  2. 21 Mar, 2014 3 commits
  3. 08 Mar, 2014 1 commit
  4. 07 Mar, 2014 2 commits
  5. 17 Feb, 2014 1 commit
  6. 10 Feb, 2014 1 commit
  7. 16 Jan, 2014 2 commits
  8. 14 Jan, 2014 3 commits
  9. 13 Jan, 2014 4 commits
  10. 10 Jan, 2014 3 commits
    • Max Cai's avatar
      Correctness: floating point equality using bits instead of ==. · 79b311c1
      Max Cai authored
      Special values for float and double make it inaccurate to test the equality with ==.
      The main Java library uses the standard Object.equals() implementation for all fields,
      which for floating point fields means Float.equals() or Double.equals(). They define
      equality as bitwise equality, with all NaN representations normalized to the same bit
      sequence (and therefore equal to each other). This test checks that the nano
      implementation complies with Object.equals(), so NaN == NaN and +0.0 != -0.0.
      
      Change-Id: I97bb4a3687223d8a212c70cd736436b9dd80c1d7
      79b311c1
    • Max Cai's avatar
      Don't serialize required fields whose 'has' flags are unset. · 1b1735ce
      Max Cai authored
      Change-Id: Ibbe944fff83e44a8f2206e18ee9ec6f10661297a
      1b1735ce
    • Max Cai's avatar
      Extension overhaul. · e3714f00
      Max Cai authored
      - Get rid of TypeLiteral<T>. It was introduced to read the component
        type of a List<T> at runtime. But we use arrays everywhere else,
        and we can always read the component type of an array type at
        runtime.
      - Properly read/write "minor" types (e.g. sint32, sfixed32). The old
        implementation could only read/write data as the "typical" types
        (one per Java type), e.g. java.lang.Integer -> int32, java.lang.Long
        -> int64. So if e.g. an extension specifies sfixed32 as the type, it
        would be read/written in the totally incompatible int32 format.
      - Properly serialize repeated packed fields. The old implementation
        doesn't do packed serialization. As an added bonus, and to be more
        aligned with the rest of protobuf nano / main, repeated packable
        extensions can deserialize both packed and non-packed data.
      - Split Extension class into a hierarchy so under typical usage a
        large chunk of code dealing with primitive type extensions can be
        removed by ProGuard.
      
      Bug: https://code.google.com/p/android/issues/detail?id=62586
      Change-Id: I0d692f35cc2a8ad3a5a1cb3ce001282b2356b041
      e3714f00
  11. 19 Dec, 2013 2 commits
  12. 12 Dec, 2013 1 commit
    • Andrew Flynn's avatar
      Fix MessageNanoPrinter for accessors · 02a9ea00
      Andrew Flynn authored
      accessors mode switches proto fields away from being public fields (which is
      how MessageNanoPrinter found which fields to print via reflection). Add a
      pass through the methods looking for generated accessor methods to print
      those as well.
      
      Change-Id: I7c47853ecbd5534086f44b25a89dbbe56f63ed03
      02a9ea00
  13. 10 Dec, 2013 5 commits
  14. 09 Dec, 2013 1 commit
    • Andrew Flynn's avatar
      Nano: don't generate accessor methods for nested methods · c997c136
      Andrew Flynn authored
      For nested message objects, don't generate accessor methods because they have
      a default value that is not a valid value (null), so there is no reason to have
      get/set/has/clear methods for them. Clients and protos (while serializing) can
      check against the invalid value to see if it's been set.
      
      Change-Id: Ic63400889581271b8cbcd9c45c84519d4921fd4b
      c997c136
  15. 06 Dec, 2013 1 commit
  16. 05 Dec, 2013 1 commit
  17. 23 Nov, 2013 1 commit
  18. 22 Nov, 2013 1 commit
  19. 21 Nov, 2013 1 commit
  20. 18 Nov, 2013 2 commits
  21. 15 Nov, 2013 1 commit