From 86ff8ee50b59c6cfb0e4b502ad619bdf3f3c1981 Mon Sep 17 00:00:00 2001 From: C R Onjob Date: Tue, 7 Oct 2014 01:00:02 +0800 Subject: [PATCH] Automatic commit of irc logs Domestic happiness and faithful friends. --- irc/#ipdf.log | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/irc/#ipdf.log b/irc/#ipdf.log index 93c9097..dd6b549 100644 --- a/irc/#ipdf.log +++ b/irc/#ipdf.log @@ -6244,3 +6244,15 @@ 18:47 <@matches> )Un(Fortunately 18:47 <@matches> I have invented a new gramatical construct-thing 18:47 * matches adds it to the list of results +--- Day changed Mon Oct 06 2014 +18:02 <@matches> So the good news is I worked out the transform, the bad news is it's yet another horrible hack +18:03 <@matches> Which will undoubtably be extremely slow if I use Gmprat +19:01 <@matches> It's amazing how useful a "grid.svg" that is just lines which should in theory be one pixel apart is +19:01 <@matches> If we could draw it in a different colour it would be even more useful +19:01 <@matches> But the clock of doom is counting down to the epsilon of time +19:17 <@matches> A quick bit of later: http://szmoore.net/ipdf/fox-vector+grid.png +19:20 <@matches> Wow that took 16 minutes +19:20 <@matches> ... 19 if you count the last 3... +19:20 <@matches> I'm running out of epsilons +19:21 <@matches> If I represent the amount of time I have left on the project as a floating point number, then a single second is below the epsilon for floats, therefore each second will not affect the amount of time I have left, therefore I will never have to finish +19:21 * matches resists the urge to verify if a single second is actually below epsilon or not -- 2.20.1