[lmi-commits] [lmi] master bcd8612 2/5: Improve terminology

[Greg Chicares]

branch: master
commit bcd861253f79a1051cbac1c72c052570f08fbfd1
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Improve terminology
    
    Some questions were ambiguous with the old term, but not with the new.
    
    For example, can a 1035 exchange be applied to a policy that's in force?
    The exchange must occur as of the issue date; but does it precede, or
    follow, issuance of the policy...or are the two events simultaneous? A
    tax attorney might say they both occur at the same moment, while the
    designer of an admin system would say that's impossible--even if two
    functions are called at the same moment in parallel, one will surely
    finish before the other. But both can agree that the two events both
    occur as of the issue date.
    
    For another example, can a GPT adjustment event occur on a policy that
    is not regarded as "in force"? Some might reserve that term for policies
    that have attained their first anniversary, or that were issued in a
    previous calendar year. Most would agree that on the issue date a policy
    is "in force", but is not to be considered an "inforce" policy because
    it is instead "new business". The question "was it issued today?" avoids
    the ambiguity.
    
    The old and new terms have opposite senses: a policy that's about to be
    issued today is not yet in force; and a policy in its second year, which
    all would agree is "in force" from every point of view, cannot be issued
    today. No committed code need be changed, because none uses this field.
---
 gpt_commutation_functions.hpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gpt_commutation_functions.hpp b/gpt_commutation_functions.hpp
index 7d824fa..60ef177 100644
--- a/gpt_commutation_functions.hpp
+++ b/gpt_commutation_functions.hpp
@@ -102,7 +102,7 @@ struct gpt_scalar_parms
     mcenum_defn_life_ins defn_life_ins   {             mce_gpt};
     mcenum_dbopt_7702    dbopt_7702      {mce_option1_for_7702};
     double               gross_1035      {                 0.0};
-    bool                 is_inforce      {               false};
+    bool                 issued_today    {               false};
     double               inforce_glp     {                 0.0};
     double               inforce_cum_glp {                 0.0};
     double               inforce_gsp     {                 0.0};
@@ -128,7 +128,7 @@ struct gpt_scalar_parms
             && z.defn_life_ins   == defn_life_ins
             && z.dbopt_7702      == dbopt_7702
             && z.gross_1035      == gross_1035
-            && z.is_inforce      == is_inforce
+            && z.issued_today    == issued_today
             && z.inforce_glp     == inforce_glp
             && z.inforce_cum_glp == inforce_cum_glp
             && z.inforce_gsp     == inforce_gsp