Revised how Ledger handles the "current year"

Now when the Y directive sets the current year for a region, it affects
everything, as if the clock really were set back to that year.

1 files changed, 6 insertions, 8 deletions

diff --git a/src/item.h b/src/item.h
index 209b2dc2..8018db9a 100644
--- a/src/item.h
+++ b/src/item.h
@@ -162,14 +162,12 @@ public:
           const optional<value_t>& value              = none,
           const bool               overwrite_existing = true);
 
-  virtual void parse_tags(const char *                p,
-                          scope_t&                    scope,
-                          bool                        overwrite_existing = true,
-                          optional<date_t::year_type> current_year       = none);
-  virtual void append_note(const char *                p,
-                           scope_t&                    scope,
-                           bool                        overwrite_existing = true,
-                           optional<date_t::year_type> current_year       = none);
+  virtual void parse_tags(const char * p,
+                          scope_t&     scope,
+                          bool         overwrite_existing = true);
+  virtual void append_note(const char * p,
+                           scope_t&     scope,
+                           bool         overwrite_existing = true);
 
   static bool use_effective_date;