[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi-commits] [lmi] master 9d19cdc 3/6: Resolve a marked defect: need no
From: |
Greg Chicares |
Subject: |
[lmi-commits] [lmi] master 9d19cdc 3/6: Resolve a marked defect: need not check input for NaN [403] |
Date: |
Tue, 31 Jan 2017 21:20:57 +0000 (UTC) |
branch: master
commit 9d19cdcd903e6e3d4bcf192f8875bdc108e05467
Author: Gregory W. Chicares <address@hidden>
Commit: Gregory W. Chicares <address@hidden>
Resolve a marked defect: need not check input for NaN [403]
Checking input for NaN was a cute idea, but if it were worth doing, it
should be done for all input, not just sequences. To the best of our
knowledge, no end user has ever encountered a NaN. And NaNs do tend to
make themselves manifest anyway.
---
input_sequence.cpp | 1 -
1 file changed, 1 deletion(-)
diff --git a/input_sequence.cpp b/input_sequence.cpp
index e7a7eda..182fb59 100644
--- a/input_sequence.cpp
+++ b/input_sequence.cpp
@@ -326,7 +326,6 @@ void InputSequence::realize_vector()
<< LMI_FLUSH
;
}
- // TODO ?? Also check whether value_number is a NaN.
if(interval_i.value_is_keyword && "insane" == interval_i.value_keyword)
{
fatal_error()
- [lmi-commits] [lmi] master updated (d040068 -> 2286e57), Greg Chicares, 2017/01/31
- [lmi-commits] [lmi] master ca6ff86 1/6: Improve documentation, Greg Chicares, 2017/01/31
- [lmi-commits] [lmi] master 9d19cdc 3/6: Resolve a marked defect: need not check input for NaN [403],
Greg Chicares <=
- [lmi-commits] [lmi] master 5c76c96 2/6: Initialize local POD variables at point of declaration [404], Greg Chicares, 2017/01/31
- [lmi-commits] [lmi] master b6a43b5 5/6: Test input-sequence keywords-only switch [401], Greg Chicares, 2017/01/31
- [lmi-commits] [lmi] master 2286e57 6/6: Transliterate some unit-test examples for concinnity, Greg Chicares, 2017/01/31
- [lmi-commits] [lmi] master 4ecdb09 4/6: Resolve a marked defect: duration keywords already tested [402], Greg Chicares, 2017/01/31