8d75635505
When a transaction posts to two commodities without specifying the conversion price, we generate a price which makes it balance (cf http://hledger.org/manual.html#prices). Until now, these generated prices were always shown with full precision (all available decimal digits) so that a manual calculation with the displayed numbers would agree. If there's just one posting in the commodity being priced, we can use an exact total price and the precision is no problem. But if there are multiple postings in the commodity being priced, we must show the averaged unit price. This can be an irrational number, which with our current Decimal-based implementation would display an excessive 255 decimal digits. So in this case we now set the price's display precision to the sum of the (max) display precisions of the commodities involved. An example: hledgerdev -f- print <<< 1/1 c C 10.00 c C 11.00 d D -320.00 >>> 2015/01/01 c C 10.00 @ D 15.2381 c C 11.00 @ D 15.2381 d D -320.00 >>>=0 There might still be cases where this will show more price decimal places than necessary. For now, YAGNI. |
||
|---|---|---|
| .. | ||
| Account.hs | ||
| AccountName.hs | ||
| Amount.hs | ||
| Commodity.hs | ||
| Dates.hs | ||
| Journal.hs | ||
| Ledger.hs | ||
| OutputFormat.hs | ||
| Posting.hs | ||
| RawOptions.hs | ||
| TimeLog.hs | ||
| Transaction.hs | ||
| Types.hs | ||