On 7/1/14 7:45 PM, Martin Blais wrote:
Alright... so here's the punchline: I'm claiming that if Ledger or
HLedger gave up on balance assertions attached to postings, if you
separated them as I do, just that change, you would both very likely be
able to guarantee order-independence w.r.t. your input files! Think
Indeed we would, of course, at the cost of giving up intra-day assertions.
I don't feel too strongly about intra-day assertions either way. But I
think hledger needs to support Ledger's style of assertions, at least.
(Though I just added a --ignore-assertions flag as an alternative.)
We could also name and implement all of these three kinds of assertions:
- ledger's single-commodity, ordered, posting-based assertions
- hledger's multi-commodity, ordered, posting-based assertions (using ==)
- beancount's order-independent, directive-based assertions (do these
assert one commodity or all of them ?)
This gives most power and compatibility.. but also more feature bloat.
Anyway I probably shouldn't think about supporting beancount format with
hledger's main parser, due to its other differences.
--
---
You received this message because you are subscribed to the Google Groups "Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
