Quick Links: |
Provide conversions between date/time objects and FIX strings. More...
Namespaces | |
namespace | bdlt |
bdlt::FixUtil | namespace for FIX date/time conversion functions |
bdlt::FixUtil
, containing functions that convert bdlt
date, time, and datetime objects to and from ("generate" and "parse", respectively) corresponding string representations that are compliant with the FIX standard. The version of the FIX standard that is the basis for this component can be found at: http://www.fixtradingcommunity.org/FIXimate/FIXimate3.0/latestEP/en/
FIX.5.0SP2_EP208/fix_datatypes.html
FixUtil
functions support what FIX refers to as complete representations in extended format. We first present a brief overview before delving into the details of the FIX representations that are supported for each of the relevant bdlt
vocabulary types. generate
and generateRaw
) takes a bdlt
object and a char *
buffer, bsl::string
, or bsl::ostream
, and writes a FIX representation of the object to the buffer, string, or stream. The "raw" functions are distinguished from their non-"raw" counterparts in three respects: char *
buffer is not supplied to the generateRaw
functions. generateRaw
functions do not output a null terminator. generate
functions that provide an int bufferLength
parameter truncate the generated output to bufferLength
characters. (Neither the generateRaw
functions nor the generate
functions taking bsl::string
or bsl::ostream
do any truncation of their generated output.) char *
buffer or string, or a reference to the stream, is returned. (Note that the generating functions also take an optional bdlt::FixUtilConfiguration
object, which is discussed shortly.) parse
) take the address of a target bdlt
object and a const char *
(paired with a length
argument) or bsl::string_view
, and loads the object with the result of parsing the character string. Since parsing can fail, the parse functions return an int
status value (0 for success and a non-zero value for failure). Note that, besides elementary syntactical considerations, the validity of parsed strings are subject to the semantic constraints imposed by the various isValid*
class methods (i.e., Date::isValidYearMonthDay
, Time::isValid
, etc.). bdlt
components commonly refer to as a timezone offset (or simply as an offset; e.g., see bdlt_datetimetz
). For example, the FIX string 20020317-15:46:00+04:00
has a timezone offset of +04:00
, indicating a timezone 4 hours ahead of UTC. millisecond
and microsecond
attributes of a bdlt::Datetime
or bdlt::Time
object. For example, the Time
value (and FIX string) 15:46:09.330
has a millisecond
attribute value of 330; i.e., a fractional second of .33. generate
and generateRaw
functions are a straightforward transposition of the attributes of the source bdlt
value into an appropriate FIX format, and are best illustrated by a few examples. Note that for Datetime
, DatetimeTz
, and Time
, the fractional second is generated with the precision specified in the configuration. Also note that for TimeTz
, no fractional second is generated (as per the FIX specification for "TZTimeOnly"). +--------------------------------------+---------------------------------+ | Object Value | Generated FIX String | | | (using default configuration) | +======================================+=================================+ | Date(2002, 03, 17) | 20020317 | +--------------------------------------+---------------------------------+ | Time(15, 46, 09, 330) | 15:46:09.330 | +--------------------------------------+---------------------------------+ | Datetime(Date(2002, 03, 17) | | | Time(15, 46, 09, 330)) | 20020317-15:46:09.330 | +--------------------------------------+---------------------------------+ | DateTz(Date(2002, 03, 17), -120) | 20020317-02:00 | +--------------------------------------+---------------------------------+ | TimeTz(Time(15, 46, 09, 330), 270) | 15:46:09+04:30 | +--------------------------------------+---------------------------------+ | DatetimeTz(Datetime( | | | Date(2002, 03, 17), | | | Time(15, 46, 09, 330)), | | | 0) | 20020317-15:46:09.330+00:00 | +--------------------------------------+---------------------------------+
bdlt::DateTz
. generate
and generateRaw
functions provide an optional configuration parameter. This optional parameter, of type FixUtilConfiguration
, enables configuration of two aspects of FIX string generation: Z
is output for the timezone offset instead of +00:00
(UTC). FixUtilConfiguration
has two attributes that directly correspond to these aspects. In addition, for generate methods that are not supplied with a configuration argument, a process-wide configuration takes effect. See bdlt_fixutilconfiguration
for details. FixUtilConfiguration
argument). Moreover, the process-wide configuration has no effect on parsing either. Instead, the parse methods automatically treat +00:00
and Z
as equivalent timezone offsets (both denoting UTC). Finally, the parsing allows seconds to be optionally specified in all types, which is in contradiction to some of the types in the referenced FIX protocol specification. Date
, Time
, and Datetime
. If a timezone offset is parsed for a Date
, it must be valid, so it can affect the status value that is returned in that case, but it is otherwise ignored. For Time
and Datetime
, any timezone offset present in the parsed string will affect the resulting object value (unless the timezone offset denotes UTC) because the result is converted to UTC. If the timezone offset is absent, it is treated as if +00:00
were specified: +------------------------------------+-----------------------------------+ | Parsed FIX String | Result Object Value | +====================================+===================================+ | 20020317-02:00 | Date(2002, 03, 17) | | | # timezone offset ignored | +------------------------------------+-----------------------------------+ | 20020317-02:65 | Date: parsing fails | | | # invalid timezone offset | +------------------------------------+-----------------------------------+ | 15:46:09.330+04:30 | Time(11, 16, 09, 330) | | | # converted to UTC | +------------------------------------+-----------------------------------+ | 15:46:09.330+04:30 | TimeTz(Time(15, 46, 09, 330), | | | 270) | +------------------------------------+-----------------------------------+ | 15:46:09.330 | TimeTz(Time(15, 46, 09, 330), | | | 0) | | | # implied '+00:00' | +------------------------------------+-----------------------------------+ | 20020317-23:46:09.222-05:00 | Datetime(Date(2002, 03, 18), | | | Time(04, 46, 09, 222)) | | | # carry into 'day' attribute | | | # when converted to UTC | +------------------------------------+-----------------------------------+
day
attribute of the Date
component of the resulting Datetime
value. Note that if such a carry causes an underflow or overflow at the extreme ends of the valid range of dates (0001/01/01 and 9999/12/31), then parsing for Datetime
fails. .0
were specified. When the fractional second is present, it can have one or more digits (in divergence with the referenced FIX protocol document, which indicates the fractional second may be unspecified or have a positive multiple of three digits). Although FIX has provision for picosecond (or finer) time resolution, be aware that bdlt
is limited to microsecond resolution. If more than six digits are included in the fractional second, values are rounded to a full microsecond; i.e., values greater than or equal to .5 microseconds are rounded up. These roundings may incur a carry of one second into the second
attribute: +--------------------------------------+---------------------------------+
| Parsed FIX String | Result Object Value |
+======================================+=================================+
| 15:46:09.1 | Time(15, 46, 09, 100) |
+--------------------------------------+---------------------------------+
| 15:46:09-05:00 | TimeTz(Time(15, 46, 09), -300) |
| | # implied '.0' |
+--------------------------------------+---------------------------------+
| 15:46:09.99999949 | Time(15, 46, 09, 999, 999) |
| | # truncate last two digits |
+--------------------------------------+---------------------------------+
| 15:46:09.9999995 | Time(15, 46, 10, 000) |
| | # round up and carry |
+--------------------------------------+---------------------------------+
Datetime
and DatetimeTz
, if a carry due to rounding of the fractional second causes an overflow at the extreme upper end of the valid range of dates (i.e., 9999/12/31), then parsing fails. bdlt::Time
or bdlt::Datetime
. Hence, they are not produced by any of the FixUtil
generate functions. However, positive leap seconds are supported by the parse functions. A leap second is recognized when the value parsed for the second
attribute of a Time
is 60 -- regardless of the values parsed for the hour
, minute
, and millisecond
attributes. Note that this behavior is more generous than that afforded by the FIX specification (which indicates that a positive leap second can only be represented as "23:59:60Z"). second
attribute is taken to be 59, so that the value of the Time
object can be validly set; then an additional second is added to the object. Note that the possible carry incurred by a leap second (i.e., when loading the result of parsing into a Datetime
or DatetimeTz
object) has the same potential for overflow as may occur with fractional seconds that are rounded up (although in admittedly pathological cases). bdlt
, i.e., as the default value for bdlt::Time
, "24:00:00.000" is not a valid string in the FIX protocol. As per other methods acting upon 24:00 within bdlt
, an hour
attribute value of 24 is mapped to 0 by the generate functions provided by this component: +------------------------------------+-----------------------------------+ | Source Object Value | Generated FIX String | +====================================+===================================+ | Time(24, 0, 0, 0) | 00:00:00.000 | +------------------------------------+-----------------------------------+ | Datetime(Date(2002, 03, 17), | 20020317-00:00:00.000 | | Time(24, 0, 0, 0)) | | +------------------------------------+-----------------------------------+
bdlt::FixUtil
parse methods. [+-:.Z]
are literal characters that can occur in FIX strings. The characters [YMDhms]
each denote a decimal digit, {}
brackets optional elements, ()
is used for grouping, and |
separates alternatives: <Generated Date> ::= <DATE> <Parsed Date> ::= <Parsed DateTz> <Generated DateTz> ::= <DATE><ZONE> <Parsed DateTz> ::= <DATE>{<ZONE>} <Generated Time> ::= <TIME FLEXIBLE> <Parsed Time> ::= <Parsed TimeTz> <Generated TimeTz> ::= <TIME FIXED><ZONE> <Parsed TimeTz> ::= <TIME FLEXIBLE>{<ZONE>} <Generated Datetime> ::= <DATE>-<TIME FLEXIBLE> <Parsed Datetime> ::= <Parsed DatetimeTz> <Generated DatetimeTz> ::= <DATE>-<TIME FLEXIBLE><ZONE> <Parsed DatetimeTz> ::= <DATE>-<TIME FLEXIBLE>{<ZONE>} <DATE> ::= YYYYMMDD <TIME FIXED> ::= hh:mm:ss <TIME FLEXIBLE> ::= hh:mm{:ss{.s+}} <ZONE> ::= ((+|-)hh{:mm})|Z # timezone offset, the colon # and minute attribute are # optional during parsing
generate
function and two parse
functions. const bdlt::Date date(2005, 1, 31); // 2005/01/31 const bdlt::Time time(8, 59, 59, 123); // 08:59:59.123 const int tzOffset = 240; // +04:00 (four hours west of UTC)
bdlt::DatetimeTz
object for which a corresponding FIX-compliant string will be generated shortly: const bdlt::DatetimeTz sourceDatetimeTz(bdlt::Datetime(date, time), tzOffset);
sourceDatetimeTz
to stdout
: bsl::cout << sourceDatetimeTz << bsl::endl;
31JAN2005_08:59:59.123000+0400
generate
function to produce a FIX-compliant string for sourceDatetimeTz
, writing the output to a bsl::ostringstream
, and assert that both the return value and the string that is produced are as expected: bsl::ostringstream oss; const bsl::ostream& ret = bdlt::FixUtil::generate(oss, sourceDatetimeTz); assert(&oss == &ret); const bsl::string fix = oss.str(); assert(fix == "20050131-08:59:59.123+04:00");
bdlt::DatetimeTz
object, and assert that the parse was successful and that the target object has the same value as that of the original (i.e., sourceDatetimeTz
): bdlt::DatetimeTz targetDatetimeTz; int rc = bdlt::FixUtil::parse(&targetDatetimeTz, fix.c_str(), static_cast<int>(fix.length())); assert( 0 == rc); assert(sourceDatetimeTz == targetDatetimeTz);
fix
string a second time, this time loading the result into a bdlt::Datetime
object (instead of a bdlt::DatetimeTz
): bdlt::Datetime targetDatetime; rc = bdlt::FixUtil::parse(&targetDatetime, fix.c_str(), static_cast<int>(fix.length())); assert( 0 == rc); assert(sourceDatetimeTz.utcDatetime() == targetDatetime);
bdlt::FixUtilConfiguration
object to influence the format of the FIX strings that are generated by this component by passing that configuration object to generate
. We also take this opportunity to illustrate the flavor of the generate
functions that outputs to a char *
buffer of a specified length. bdlt::FixUtilConfiguration
object that indicates how we would like to affect the generated output FIX string. In this case, we want to have microsecond precision displayed: bdlt::FixUtilConfiguration configuration; configuration.setFractionalSecondPrecision(6);
char *
buffer that will be used to stored the generated string. A buffer of size bdlt::FixUtil::k_DATETIMETZ_STRLEN + 1
is large enough to hold any string generated by this component for a bdlt::DatetimeTz
object, including a null terminator: const int BUFLEN = bdlt::FixUtil::k_DATETIMETZ_STRLEN + 1; char buffer[BUFLEN];
generate
function that accepts our configuration
to produce a FIX-compliant string for sourceDatetimeTz
, this time writing the output to a char *
buffer, and assert that both the return value and the string that is produced are as expected. Note that in comparing the return value against BUFLEN - 1
we account for the fact that, although a null terminator was generated, it is not included in the character count returned by generate
. Also note that we use bsl::strcmp
to compare the resulting string knowing that we supplied a buffer having sufficient capacity to accommodate a null terminator: rc = bdlt::FixUtil::generate(buffer, BUFLEN, sourceDatetimeTz, configuration); assert(BUFLEN - 1 == rc); assert( 0 == bsl::strcmp(buffer, "20050131-08:59:59.123000+04:00"));
bdlt::DatetimeTz
object, and assert that the parse was successful and that the target object has the same value as that of the original (i.e., sourceDatetimeTz
). Note that BUFLEN - 1
is passed and not BUFLEN
because the former indicates the correct number of characters in buffer
that we wish to parse: rc = bdlt::FixUtil::parse(&targetDatetimeTz, buffer, BUFLEN - 1); assert( 0 == rc); assert(sourceDatetimeTz == targetDatetimeTz);
buffer
a second time, this time loading the result into a bdlt::Datetime
object (instead of a bdlt::DatetimeTz
): rc = bdlt::FixUtil::parse(&targetDatetime, buffer, BUFLEN - 1); assert( 0 == rc); assert(sourceDatetimeTz.utcDatetime() == targetDatetime);
configuration
to display the bdlt::DatetimeTz
without fractional seconds: configuration.setFractionalSecondPrecision(0); rc = bdlt::FixUtil::generate(buffer, BUFLEN, sourceDatetimeTz, configuration); assert(BUFLEN - 8 == rc); assert( 0 == bsl::strcmp(buffer, "20050131-08:59:59+04:00"));