- Generated by
1.9.8
|
BDE 4.14.0 Production release
|
Externalization of fundamental types to a bsl::streambuf.
bsl::streambuf output for fundamentalsThis component implements a bsl::streambuf output stream class, bslx::StreambufOutStream, that provides platform-independent output methods ("externalization") on values, and arrays of values, of fundamental types, and on bsl::string.
This component is intended to be used in conjunction with the unexternalization component. Each output method of bslx::StreambufOutStream writes a value or a homogeneous array of values to a bsl::streambuf. The values are formatted to be readable by the corresponding bslx::StreambufInStream method. In general, the user cannot rely on any other mechanism to read data written by bslx::StreambufOutStream unless that mechanism explicitly states its ability to do so.
The supported types and required content are listed in the bslx package-level documentation under "Supported Types".
Note that the values are stored in big-endian (i.e., network byte order) format.
Note that output streams can be invalidated explicitly and queried for validity. Writing to an initially invalid stream has no effect. Whenever an output operation fails, the stream should be invalidated explicitly.
BDEX provides two concepts that support versioning the BDEX serialization format of a type: version and versionSelector. A version is a 1-based integer indicating one of the supported formats (e.g., format 1, format 2, etc.). A versionSelector is a value that is mapped to a version for a type by the type's implementation of maxSupportedBdexVersion.
Selecting a value for a versionSelector is required at two different points: (1) when implementing a new version format within the bdexStreamIn and bdexStreamOut methods of a type, and (2) when implementing code that constructs a BDEX OutStream. In both cases, the value should be a compile-time-selected value.
When a new version format is implemented within the bdexStreamIn and bdexStreamOut methods of a type, a new mapping in maxSupportedBdexVersion should be created to expose this new version with a versionSelector. A simple - and the recommended - approach is to use a value having the pattern "YYYYMMDD", where "YYYYMMDD" corresponds to the "go-live" date of the corresponding version format.
When constructing an OutStream, a simple approach is to use the current date as a compile-time constant value. In combination with the recommended selection of versionSelector values for maxSupportedBdexVersion, this will result in consistent and predictable behavior while externalizing types. Note that this recommendation is chosen for its simplicity: to ensure the largest possible audience for an externalized representation, clients can select the minimum date value that will result in the desired version of all types externalized with operator<< being selected.
See the bslx package-level documentation for more detailed information about versioning.
This section illustrates intended use of this component.
A bslx::StreambufOutStream can be used to externalize values in a platform-neutral way. Writing out fundamental C++ types and bsl::string requires no additional work on the part of the client; the client can simply use the stream directly. The following code serializes a few representative values using a bslx::StreambufOutStream, compares the contents of this stream to the expected value, and then writes the contents of this stream's buffer to stdout.
First, we create a bslx::StreambufOutStream with an arbitrary value for its versionSelector and externalize some values:
Then, we compare the contents of the stream to the expected value:
Finally, we print the stream's contents to bsl::cout.
Executing the above code results in the following output:
See the bslx_streambufinstream component usage example for a more practical example of using bslx streams.
1.9.8