[lmi-commits] [lmi] master e1c1f2b: Inititialize all table numbers to zero

[Greg Chicares]

branch: master
commit e1c1f2b537f17bd46c26ff729e04e6346e4b9723
Author: Gregory W. Chicares <address@hidden>
Commit: Gregory W. Chicares <address@hidden>

    Inititialize all table numbers to zero
    
    Formerly, DB_CurrCoiTable1 and DB_CurrCoiTable2 were initialized to 999,
    with a comment stating that 0 would be wrong. However, all other tables,
    including DB_CurrCoiTable, have always been initialized to 0 by default,
    clearly meaning "invalid" because there is no table zero. Now, every
    table, including these two, is initialized the same way, to zero.
---
 dbdict.cpp | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/dbdict.cpp b/dbdict.cpp
index b258b04..0e487fe 100644
--- a/dbdict.cpp
+++ b/dbdict.cpp
@@ -558,13 +558,6 @@ void DBDictionary::InitDB()
     Add({DB_MaxWdGenAcctValMult   , 1.0});
     Add({DB_MaxWdSepAcctValMult   , 1.0});
 
-    // These aren't always right, but zero is never right.
-
-    Add({DB_CurrCoiTable0Limit    , dbl_inf});
-    Add({DB_CurrCoiTable1         , 999});
-    Add({DB_CurrCoiTable1Limit    , dbl_inf});
-    Add({DB_CurrCoiTable2         , 999});
-
     // Usually the maximum is a reciprocal, e.g., 1/11 or 1/12; for
     // greatest precision, store the reciprocal of that reciprocal,
     // e.g., 11 or 12.
@@ -574,6 +567,8 @@ void DBDictionary::InitDB()
     Add({DB_CoiResetMinDate       , calendar_date::gregorian_epoch_jdn});
     Add({DB_CoiResetMaxDate       , calendar_date::last_yyyy_date_jdn });
 
+    Add({DB_CurrCoiTable0Limit    , dbl_inf});
+    Add({DB_CurrCoiTable1Limit    , dbl_inf});
     Add({DB_GuarIntSpread         , dbl_inf});
     Add({DB_SpecAmtLoadLimit      , dbl_inf});
     Add({DB_DynSepAcctLoadLimit   , dbl_inf});