| 7e979c369670feea99b9aff42bc366a903cf7049 |
|
30-Sep-2016 |
mukesh agrawal <quiche@google.com> |
various: fix comment URL
The comment about the naming of death tests
includes a link to the GoogleTest documentation.
But that link has a superfluous ')' at the end.
Remove the stray ')'.
Bug: 32483646
Test: ./runtests.sh (on angler)
Change-Id: I7163598f36d2792e572d7f8b8394c65ba12a0301
/system/connectivity/wifilogd/tests/byte_buffer_unittest.cpp
|
| 937164df3f181a273589ed0c12dcc3729bbd1d6d |
|
21-Oct-2016 |
mukesh agrawal <quiche@google.com> |
ByteBuffer: allow chaining of AppendOrDie()
In some of our calling contexts, it would be more
convenient to initialize a const ByteBuffer in a
single expression.
To that end:
- Update ByteBuffer, to allow chaining of calls
to AppendOrDie().
- Updating existing uses of ByteBuffer, to make
use of this new capability (where appropriate).
Bug: 32317095
Test: ./runtests.sh (on angler)
Change-Id: I39585b204ee6cc112ebe233670be8a9ab30d584b
/system/connectivity/wifilogd/tests/byte_buffer_unittest.cpp
|
| 3d8db0877bb66bfea17e37e12a586b4b29440963 |
|
01-Oct-2016 |
mukesh agrawal <quiche@google.com> |
add ByteBuffer
ByteBuffer provides a simple way of concatenating data, such
as we might want to do when generating a protocol packet.
ByteBuffer is implemented as a class template, rather than a
simple class, because we want to be able to allocate a ByteBuffer
on the stack. For stack allocation, the object size must be
known at compile-time. Hence, ByteBuffer is a class template,
parameterized on the buffer size.
Bug: 31861967
Test: ./runtests.sh (on bullhead)
Change-Id: I1fe89a9cdcf34cf380365b3aad2537edca87a424
/system/connectivity/wifilogd/tests/byte_buffer_unittest.cpp
|