From f554c93c20e940e6fb04e8bd0685896306e92653 Mon Sep 17 00:00:00 2001 From: C R Onjob Date: Sat, 6 Sep 2014 01:00:02 +0800 Subject: [PATCH] Automatic commit of irc logs Q: "What is the burning question on the mind of every dyslexic existentialist?" A: "Is there a dog?" --- irc/#ipdf.log | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/irc/#ipdf.log b/irc/#ipdf.log index ddae826..65452d2 100644 --- a/irc/#ipdf.log +++ b/irc/#ipdf.log @@ -4228,3 +4228,21 @@ 23:42 < matches> How I have missed you 23:42 < matches> void Foo() {if (m_next != NULL) m_next->Foo();} 23:42 < matches> <3 +--- Day changed Fri Sep 05 2014 +09:26 < matches> It sort of kind of works +09:26 < matches> Except when it breaks +09:26 < matches> ParanoidNumber::Simplify needs improvement +09:26 < matches> Also operator+= +09:26 < matches> operator-= +09:26 < matches> operator*= +09:26 < matches> and operator/= +09:26 < matches> But it's definitely a number +09:27 < matches> It just occasionally does things in totally the wrong order' +09:28 < matches> So basically the idea is if you have an inexact (or overflow/underflow) operation, you delay it, and then in theory you can rearrange the operations so you have a smaller error... +09:28 < matches> It seems to give better results than floats for tests/paranoidcalculator +09:29 < matches> But that might be because it is initialised off 3/10 and the float starts at 0.3 +09:30 < matches> It could all be totally useless +09:30 < matches> It probably is totally useless +09:31 < matches> I have a hunch that even if it's terrible it might beat true arbitrary precision arithmetic +09:31 < matches> In terms of actually being able to use it +09:31 < matches> Who needs mathematics when you have blind intuition... -- 2.20.1