* nugget <[email protected]> [2020-08-10 02:52]: > - The design of Beancounts D() technically allows allows higher > precision (float) numbers as input. > - But the design philosophy does not. It requires string typed numbers > with maximum precision to the second digit. Higher precision is not > supported and might cause problems. > - It is up to the user to to deal with higher precisions. For example, > treating reminders of divisions. There is no general solution on how to > treat this. > > This works very well for me, now that I know it. > Thanks all for your replies. > > best, > nugget > > On Sunday, August 9, 2020 at 11:15:33 PM UTC+2, Daniele Nicolodi wrote: > > > > On 08/08/2020 10:41, Daniele Nicolodi wrote: > > > Another thing to potentially consider is to reduce the number of decimal > > > digits used when serializing Decimal numbers. Maybe 12 (or so) digits > > > are enough instead that the current 28. > > > > I am sure someone has a model for when 1e-12 BTC will be worth the > > equivalent of $0.01 :-) Right now we should be fine with 12 digits. > > > > Cheers, > > Dan > > > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/95c3b5fb-41cf-4409-a989-4dbf3ae2b5ffo%40googlegroups.com.
-- Martin Michlmayr https://www.cyrius.com/ -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20200810105200.GA32209%40jirafa.cyrius.com.
