[#BloombergLP-bdlb-Float-isSignalingNan-01]
= xref:BloombergLP.adoc[BloombergLP]::xref:BloombergLP/bdlb.adoc[bdlb]::xref:BloombergLP/bdlb/Float.adoc[Float]::isSignalingNan
:relfileprefix: ../../../
:mrdocs:

`isSignalingNan` overloads

== Synopses

Declared in `&lt;bdlb&lowbar;float&period;h&gt;`

Return `true` if `number` is a signaling NaN, and `false` otherwise&period;


[source,cpp,subs="verbatim,replacements,macros,-callouts"]
----
static
bool
xref:BloombergLP/bdlb/Float/isSignalingNan-07.adoc[isSignalingNan](double number);
----

[.small]#xref:BloombergLP/bdlb/Float/isSignalingNan-07.adoc[_» more&period;&period;&period;_]#

Return `true` if the specified floating point `number` has an invalid value, and `false` otherwise&period; An invalid floating&hyphen;point value (&quot;signaling NaN&quot; or &quot;SNaN&quot;)is never the result of a valid operation &hyphen;&hyphen; it must be produced deliberately (i&period;e&period;, by calling `bsl&colon;&colon;numeric&lowbar;limits&lt;float&gt;&colon;&colon;signaling&lowbar;NaN()`)&period; If an SNaN is used in a subsequent operation, the result is undefined and may result in a hardware trap leading to a signal&period; Some platforms do not support signaling NaNs, especially for single&hyphen;precision floats, and will convert an SNaN to a QNaN on assignment or copy&hyphen;initialization (including argument passing)&period; `isSignalingNan` will always return `false` on such platforms&period; Note that, because an SNaN is a NaN, if this method returns `true`, then `isNan(x)` will also return `true`&period;


[source,cpp,subs="verbatim,replacements,macros,-callouts"]
----
static
bool
xref:BloombergLP/bdlb/Float/isSignalingNan-0f.adoc[isSignalingNan](float number);
----

[.small]#xref:BloombergLP/bdlb/Float/isSignalingNan-0f.adoc[_» more&period;&period;&period;_]#


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