Implements an memory-based stream that supports the IStream interface.
This class is not inherently thread-safe. As a result, thread-safe usage between multiple threads requires higher level coordination, such as a mutex.
- class IStream
- static const uint32_t kType
- auto GetOption(Options option) const -> float
- void SetOption(Options option, float fValue)
- auto GetSharedPointer() -> SharedPointer*
- auto GetData() const -> void*
auto SetData(SharedPointer* pSharedPointer,
type nSize) -> bool
auto SetDataRaw(void* pData,
type nSize, bool bUsePointer, bool bFreePointer = true, Allocator* pAllocator = NULL) -> bool
- auto AddRef() -> int override
- auto Release() -> int override
- auto GetType() const -> uint32_t override
- Returns the type of the stream, which is different for each Stream subclass.
- auto GetAccessFlags() const -> AccessFlags override
- Returns one of enum AccessFlags.
- auto GetState() const -> FileError override
- Returns the error state of the stream.
- auto Close() -> bool override
- Closes the stream and releases resouces associated with it.
auto GetSize() const -> size_
- Returns the size of the stream, which is not the same as the size of bytes remaining to be read from the stream.
type size) -> bool override
- Sets the size of the stream, if possible.
auto GetPosition(PositionType positionType = PositionType::
Begin) const -> int override
- Gets the current read/write position within the stream.
auto SetPosition(int distance,
PositionType positionType = PositionType::
Begin) -> bool override
- Sets the read/write position of the stream.
- auto GetAvailable() const -> int override
- Returns the number of bytes available for reading.
- auto Read(void* pData, size_t nSize) -> int override
- Reads bytes from the stream given by the input count 'nSize'.
- auto Flush() -> bool override
- Flush any non-empty stream write buffers.
- auto Write(const void* pData, size_t nSize) -> int override
- Writes bytes to the stream.
- SharedPointer* mpSharedPointer
- int mnRefCount
- Pointer to memory block.
- Reference count. May or may not be in use.
- The size of the stream, in bytes.
- The size of the memory buffer, in bytes.
- bool mbResizeEnabled
- Current position within memory block.
- bool mbClearNewMemory
- True if resizing is enabled.
- float mfResizeFactor
- True if clearing of newly allocated memory is enabled.
- int mnResizeIncrement
- Specifies how capacity is increased.
enum Options Specifies policies regarding the internal operation of this class.
0 or 1. Default is disabled. If set, then the buffer is automatically resized on beyond-bounds position sets, beyond-bounds writes, and beyond-bounds SetSize calls.
1.0+ Default is 1.5. Specifies how much a resize multiplies in size; is applied before kOptionResizeIncrement. Can be 1.0 if kOptionResizeIncrement > 0.
0.0+ Default is 0.0. Specifies how much a resize increments; is applied after kOptionResizeFactor. Can be set to zero if kOptionResizeFactor is > 1.
MemoryStream:: GetType() const override
Returns the type of the stream, which is different for each Stream subclass.
This function can be used for run-time type identification. A type of zero means the type is unknown or invalid.
MemoryStream:: Close() override
Closes the stream and releases resouces associated with it.
Returns true upon success, else false. If the return value is false, GetState will give the error code. If an IStream encounters an error during operations on an open stream, it is guaranteed that you can safely call the Close function on the stream.
Sets the size of the stream, if possible.
It is debatable whether this function should be present in IStream or only in suclasses of StreamBase which are writable. For consistency with GetSize, we put the function here. But also consider that a SetSize function is not necessarily a data writing function, depending on the stream implementation.
MemoryStream:: GetPosition(PositionType positionType = PositionType:: Begin) const override
Gets the current read/write position within the stream.
The read and write positions of a stream must be the same value; you cannot have a read position that is different from a write position. However, a Stream subclass can provide such functionality if needed. Returns -1 upon error.
MemoryStream:: SetPosition(int distance,
PositionType positionType = PositionType:: Begin) override
Sets the read/write position of the stream.
If the specified position is beyond the size of a fixed stream, the position is set to the end of the stream. A writable stream subclass may provide a policy whereby setting the position beyond the end of the stream results in an increase in the stream size.
MemoryStream:: GetAvailable() const override
Returns the number of bytes available for reading.
Returns (size_type)-1 (a.k.a. kSizeTypeError) upon error. This function is non-blocking; it should return immediately.
MemoryStream:: Read(void* pData,
size_t nSize) override
Reads bytes from the stream given by the input count 'nSize'.
If less then nSize bytes are available, then those bytes will be read. Returns the number of bytes read. A return value of zero means that there were no bytes to be read or no bytes were requested to be read. A return value of zero means the end of file was reached. A return value > 0 but < 'nSize' is possible, and it does not necessarily mean that the end of the file was reached. Returns (size_type)-1 (a.k.a. kSizeTypeError) if there was an error. You can use this return value or IStream::
MemoryStream:: Flush() override
Flush any non-empty stream write buffers.
If the return value is false, GetState will give the error code. This function implements the flushing as per the underlying file system. The behavior of the Flush function varies with the underlying platform.
A common use of Flush is write a file to disk immediately in order to prevent the file from being corrupted if the application crashes before the file is closed. However, on desktop platforms such as Windows this strategy is unnecesary, as the Windows OS file flush doesn't write the file to disk as might be expected. This actually is not a problem, because the Windows OS manages files outside the process and if your process crashes the OS will take care of safely closing the files. Only if the machine power is lost or if certain kinds of kernel-level crashes occur may you lose file data.