[lmi-commits] [lmi] master 4932b16 2/2: Treat MDB as DBO1 for 7702

[Greg Chicares]

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

    Treat MDB as DBO1 for 7702
    
    MDB is defined as corridor, whereas DBO1 is max(specamt, corridor), so
    clearly MDB is like DBO1 and unlike DBO2. (This matters only for GPT,
    but the MDB DBO is likely to produce a series of adjustment events and
    material changes that would make it unusable with GPT anyway.)
---
 mc_enum_types_aux.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/mc_enum_types_aux.cpp b/mc_enum_types_aux.cpp
index 068aa92..249abd7 100644
--- a/mc_enum_types_aux.cpp
+++ b/mc_enum_types_aux.cpp
@@ -87,6 +87,7 @@ std::vector<std::string> allowed_strings_emission()
 /// GPT recognizes death benefit options A and B only. A contract
 /// might have a death benefit option other than that usual pair,
 /// but for 7702 (and 7702A) purposes it's treated as either A or B.
+/// For ROP, it might be either. For MDB, it can only be A.
 
 mcenum_dbopt_7702 effective_dbopt_7702
     (mcenum_dbopt      actual_dbopt
@@ -98,7 +99,7 @@ mcenum_dbopt_7702 effective_dbopt_7702
         case mce_option1: return mce_option1_for_7702;
         case mce_option2: return mce_option2_for_7702;
         case mce_rop:     return rop_equivalent      ;
-        case mce_mdb:     return rop_equivalent      ; // DBO3 !! reconsider
+        case mce_mdb:     return mce_option1_for_7702;
         }
     throw "Unreachable--silences a compiler diagnostic.";
 }