>>>>> Jeroen De Vlieger <[email protected]> writes: > So It is not a bug then? Transactions are parsed *and* processed in the > order that they appear in the journal file?
Yes. > Does this also mean that the ledger program assumes that the journal is > correctly ordered? I.e. when using the -e <date> flag, will ledger stop > parsing once it encounters a transaction with a later date assuming that all > the following transactions are will also be at a later date? No, the -e flag is applied only after all transactions have been read in. > In general when using time related flags like -M, -b, -e, ... Does ledger > make any assumption about the order of the transactions? I.e. should I > worry and be extra careful to make sure my transactions are in order or is > that a waste of time? No, you only need ordering for constructions within the data file (balance assertions, pricing relationships, etc). In most other ways, ordering in the data file has no effect on reporting. Some reports, like -M, even internally sort if the data has not yet been sorted. John
