[#BloombergLP-bdldfp-DecimalImpUtil_IntelDfp-parse128-0b]
= xref:BloombergLP.adoc[BloombergLP]::xref:BloombergLP/bdldfp.adoc[bdldfp]::xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp.adoc[DecimalImpUtil&lowbar;IntelDfp]::parse128
:relfileprefix: ../../../
:mrdocs:

`parse128` overloads

== Synopses

Declared in `&lt;bdldfp&lowbar;decimalimputil&lowbar;inteldfp&period;h&gt;`

Parse the specified `string` string as a 128 bit decimal floating&hyphen; point value and return the result&period; The parsing is as specified for the `strtod128` function in section 9&period;6 of the ISO&sol;EIC TR 24732 C Decimal Floating&hyphen;Point Technical Report, except that it is unspecified whether the NaNs returned are quiet or signaling&period; If `string` represents a value that absolute value exceeds the maximum value or is less than the smallest value supported by `ValueType128` type then store the value of the macro `ERANGE` into `errno` and return the value initialized to infinity or zero respectively with the same sign as specified in `string`&period; The behavior is undefined unless `input` represents a valid 128 bit decimal floating&hyphen;point number in scientific or fixed notation, and no unrelated characters precede (not even whitespace) that textual representation and a terminating null character immediately follows it&period; Note that this method does not guarantee the behavior of ISO&sol;EIC TR 24732 C when parsing NaN because the AIX compiler intrinsics return a signaling NaN&period;


[source,cpp,subs="verbatim,replacements,macros,-callouts"]
----
static
xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp/ValueType128.adoc[DecimalImpUtil&lowbar;IntelDfp::ValueType128]
xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp/parse128-0e.adoc[parse128](char const* string);
----

[.small]#xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp/parse128-0e.adoc[_» more&period;&period;&period;_]#

Parse the specified `string` string as a decimal floating&hyphen;point value and return the result, loading the specified `status` with a bit mask providing additional status information about the result&period; The supplied `&ast;status` must be 0, and may be loaded with a bit mask of `k&lowbar;STATUS&lowbar;INEXACT`, `k&lowbar;STATUS&lowbar;UNDERFLOW`, and `k&lowbar;STATUS&lowbar;OVERFLOW` constants indicating wether the conversion from text inexact, underflowed, or overflowed (or some combination) respectively&period; The parsing is as specified for the `strtod128` function in section 9&period;6 of the ISO&sol;EIC TR 24732 C Decimal Floating&hyphen;Point Technical Report, except that it is unspecified whether the NaNs returned are quiet or signaling&period; The behavior is undefined unless `input` represents a valid decimal floating&hyphen;point number in scientific or fixed notation, and no unrelated characters precede (not even whitespace) that textual representation and a terminating null character immediately follows it&period; The behavior is undefined unless `&ast;status` is 0&period; Note that this method does not guarantee the behavior of ISO&sol;EIC TR 24732 C when parsing NaN because the AIX compiler intrinsics return a signaling NaN&period; Also note that the intel decimal floating point library documents that inexact, underflow, and overflow are the possible floating point exceptions for this operation&period;


[source,cpp,subs="verbatim,replacements,macros,-callouts"]
----
static
xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp/ValueType128.adoc[DecimalImpUtil&lowbar;IntelDfp::ValueType128]
xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp/parse128-07.adoc[parse128](
    char const* string,
    unsigned int* status);
----

[.small]#xref:BloombergLP/bdldfp/DecimalImpUtil_IntelDfp/parse128-07.adoc[_» more&period;&period;&period;_]#


[.small]#Created with https://www.mrdocs.com[MrDocs]#
