When accessing from Java, you can copy in and out ranges of buffers. You can do this by-copy (which is safer but a little slower) or by-reference where you directly access underlying C++/native memory from Java. Take special care if you decide that native access is required.
When accessing from C++, you get direct access to the underlying buffer.
To make an IBuffer object that is not a Xuggler internal object, pass in null for the RefCounted parameter.
IOpenable
. If a buffer does not have an underlying resource, saving the buffer has no effect. Buffers can be read-only. Note that java model operations that manipulate an IBuffer
(for example, IType.createMethod(...)
) ensures that the same line delimiter (either "\n"
or "\r"
or "\r\n"
) is used across the whole buffer. Thus these operations may change the line delimiter(s) included in the string to be append, or replaced. However implementers of this interface should be aware that other clients of IBuffer
might not do such transformations beforehand.
This interface may be implemented by clients.
IOpenable
. If a buffer does not have an underlying resource, saving the buffer has no effect. Buffers can be read-only. Note that java model operations that manipulate an IBuffer
(for example, IType.createMethod(...)
) ensures that the same line delimiter (either "\n"
or "\r"
or "\r\n"
) is used across the whole buffer. Thus these operations may change the line delimiter(s) included in the string to be append, or replaced. However implementers of this interface should be aware that other clients of IBuffer
might not do such transformations beforehand.
This interface may be implemented by clients.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|