>>>>> Harshad RJ <[email protected]> writes: > I feel, in the case of ledger, it is possible to take a general stand on > such problems: "the order of specification doesn't matter". So it wouldn't > matter if definitions are "made before" or "parsed before" or "processed > before", etc. The user can expect consistency of results irrespective of > how the internals of the program behave.
If I rewrite the transaction processing, I will bear this in mind. > The user might have to sacrifice performance, but in the case of ledger, I > don't see a loss beyond milliseconds or seconds in a typical case (unless we > are crunching hundreds of accounts with millions of transactions, in which > case, I could attempt an alternative argument for consistency :) ). "Seconds" will never be acceptable. Ledger is meant to be run repeatedly, and waiting seconds for data to show up would drive me crazy. John -- --- 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/groups/opt_out.
