summaryrefslogtreecommitdiff
path: root/src/chain.cc
diff options
context:
space:
mode:
authorJohn Wiegley <johnw@newartisans.com>2010-05-23 15:24:02 -0600
committerJohn Wiegley <johnw@newartisans.com>2010-05-23 15:45:51 -0600
commit7bddcd676bc53c6caad7dd283be362fcd53d5721 (patch)
treed76464891f208aa9e97e21e3ee89360964fe4046 /src/chain.cc
parent847a5e4e73afd1c959f7211ceb67d6b9ab0f95d0 (diff)
downloadfork-ledger-7bddcd676bc53c6caad7dd283be362fcd53d5721.tar.gz
fork-ledger-7bddcd676bc53c6caad7dd283be362fcd53d5721.tar.bz2
fork-ledger-7bddcd676bc53c6caad7dd283be362fcd53d5721.zip
Added --rounding option, which is off by default
The purpose of this option is to add special "<Rounding>" postings, to ensure that a regiter's running total is *always* the sum of its postings. Within --rounding, these adjustment postings are missing, which was the behavior in Ledger 2.x. It can be orders of magnitude slower to turn it on for large reports with many commodities.
Diffstat (limited to 'src/chain.cc')
-rw-r--r--src/chain.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/chain.cc b/src/chain.cc
index 86f639ad..44133391 100644
--- a/src/chain.cc
+++ b/src/chain.cc
@@ -86,7 +86,8 @@ post_handler_ptr chain_post_handlers(report_t& report,
report.HANDLED(unrealized)))
handler.reset(new changed_value_posts(handler, report,
for_accounts_report,
- report.HANDLED(unrealized)));
+ report.HANDLED(unrealized),
+ report.HANDLED(rounding)));
// calc_posts computes the running total. When this appears will determine,
// for example, whether filtered posts are included or excluded from the