From 3f82f09927c0584b3769ac2d9a9624512fafe793 Mon Sep 17 00:00:00 2001
From: Justin Martin <frozenfire@php.net>
Date: Sat, 3 Dec 2011 18:43:05 +0000
Subject: [PATCH] Documented NaN behaviour. Closes bug #60346.

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@320310 c90b9560-bf6c-de11-be94-00142212c4b1
---
 language/types/float.xml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/language/types/float.xml b/language/types/float.xml
index 3fd2946641..e64debed11 100644
--- a/language/types/float.xml
+++ b/language/types/float.xml
@@ -88,6 +88,22 @@ EXPONENT_DNUM [+-]?(({LNUM} | {DNUM}) [eE][+-]? {LNUM})
   </para>
 
  </sect2>
+ 
+ <sect2 xml:id="language.types.float.nan">
+  <title>NaN</title>
+  <para>
+   Some numeric operations can result in a value represented by the constant
+   <constant>NAN</constant>. This result represents an undefined or
+   unrepresentable value in floating-point calculations. Any loose or strict
+   comparisons of this value against any other value, including itself, will
+   have a result of &false;.
+  </para>
+  <para>
+   Because <constant>NAN</constant> represents any number of different values,
+   <constant>NAN</constant> should not be compared to other values, including
+   itself, and instead should be checked for using <function>is_nan</function>.
+  </para>
+ </sect2>
 </sect1>
 
 <!-- Keep this comment at the end of the file