3 ms·
Yes, I understand the example. It's a classic floating point numbers demonstration. What I am saying is that I have not encountered a real-life case where thi
by 16bytes 9y ago
Yes, I understand the example. It's a classic floating point numbers demonstration.
What I am saying is that I have not encountered a real-life case where this would have made my life easier.
Again, it's neat, but not a real reason to move to a new language.
- petre 9y agoBanking/accounting software? Generating reports that are expected to return correct data w/o cumulative errors from flating point arithmetic? After all, Perl is the Practical Extraction and Report Language.
- 16bytes 9y agoI'm not saying there aren't applications where it is useful. If you can't tolerate errors, then you typically don't use floats in the first place. We've been running banking/accounting software for a long time without Perl 6. What I am saying is that this isn't a killer feature. It makes me go, "Oh, neat", and not, "Wow, this will make my life so much easier".
- cutler 9y agoThen I have to assume you're not working in any kind of commercial or financial sector where approximations are not acceptable. Perl 6 and Go should be lauded for solving this problem.
- 16bytes 9y agoActually, I work in analytics well inside the commercial sector. 10 digits of accuracy works most of the time, and when it doesn't there are other alternatives. As with anything there are trade-offs. I wish more languages would do this and I happily applaud Perl 6 and go for allowing sane operations in the real space without needing separate packages. But there are high quality packages for all modern languages that allow you to get precision if you need it. I'm not debating the utility of this feature, but I am saying it's not--by itself--going to make me want to pick up Perl 6 for my next project.