| a990ad5c834bd3292f8f4c5e45c7ff117ffae5ec |
|
27-Jan-2014 |
Neil Fuller <nfuller@google.com> |
Fixing FileChannel.truncate() / position()
According to the docs, after calling truncate(x), if position() > x, position()
should be made to equal x. Note: It is to be set to x, not to the actual size
of the file, since truncate() doesn't actually grow the file. Subsequent writes
will grow the file to position().
Bug: 12757843
Change-Id: I5df1fbd59f1a8610bc60575dfa7f1396baf3ed47
|
| dbde5bd893290c02bb289460fc61e48eda63daa2 |
|
20-May-2011 |
Elliott Hughes <enh@google.com> |
FileChannelImpl doesn't need to special-case O_APPEND.
...we have an OS kernel for such things.
Bug: 4455730
Change-Id: I23efc0ceaa534bffdc0da9a5ff1426ff9d56547f
|
| bbac92e691de7d570928ddfba639067978e55b06 |
|
29-Mar-2011 |
Elliott Hughes <enh@google.com> |
Add readv(2)/writev(2).
The old implementation would cheat if it was given non-direct buffers, copying
them into newly-allocated direct buffers. (The network Channel implementations
are worse: they copy all the data into a single buffer, and then read/write
that. I'll get to them eventually.)
Bug: 3107501
Change-Id: I1655bacb042e7ebcde7e5bc5cf2c71e7ce5e30af
|
| 4af0d8c99d68bcacff182699527d983a1d34fdbe |
|
28-Mar-2011 |
Elliott Hughes <enh@google.com> |
Support read-only ByteBuffers.
Buffer.array() and Buffer.arrayOffset() throw for read-only buffers. We need
to work round this. We know that this is safe because we trust ourselves not
to write to read-only buffers and because all non-direct buffers have a
backing array.
Bug: 3107501
Change-Id: I501a5f7ddba2c66d22864bf4a41b927263493293
|
| 4557728efb66c455a52b7669a8eefef7a9e54854 |
|
11-Aug-2010 |
Jesse Wilson <jessewilson@google.com> |
Moving tests to be under the libcore.* package.
This is indended to make it easier to run on VMs that restrict the packages
from which application classes can be loaded. For example, on the RI you need
to use the bootclasspath to load these tests.
Change-Id: I52193f35c5fcca18b5a3e1d280505b1e29b388af
|