>>>>> Martin Blais <[email protected]> writes: > My point with the suggestion was to highlight that a reorder-safe way to use > balance assertions that are tied to transactions is not practical; I hope my > example highlights this. You can either (1) place them where it makes sense in > your Ledger and live with occasional and difficult-to-debug failures due to > reordering, or (2) use an impractical method that is reorder-safe.
Ah, OK, I understand now. :) > (1) could be a reasonable choice, "just live with it" - depends on your view > - but requires a subtle understanding of what's going on behind the scenes. I did add a feature recently that allows me to split transactions across multiple files; I think I mentioned it here on the ML. But yes, the more of them I add, the more edit-fragile my data becomes. 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/d/optout.
