Skip to main content
12 events
when toggle format what by license comment
Nov 27, 2016 at 21:14 history edited user31159 CC BY-SA 3.0
Added bug header.
Mar 22, 2016 at 3:53 vote accept Vladimir Reshetnikov
Mar 11, 2016 at 2:33 comment added Michael E2 FWIW, I think Interval[x] returns Interval[{x-ε, x+ε}] for an ε appropriate to the precision of x.
Mar 10, 2016 at 21:38 answer added The Vee timeline score: 5
Mar 10, 2016 at 5:17 comment added Vladimir Reshetnikov IntervalMemberQ[Identity /@ Interval @ $MaxNumber, $MaxNumber] is also False. Interval @ $MaxNumber === Identity /@ Interval @ $MaxNumber is True (as expected).
Mar 10, 2016 at 3:36 comment added Michael E2 If you take the output of Interval@$MaxNumber as input, then IntervalMemberQ returns False, like the Uncompress@Compress... round-trip. Something is happening on re-parsing, I guess.
Mar 10, 2016 at 2:08 history edited Dr. belisarius
edited tags
Mar 10, 2016 at 1:50 history tweeted twitter.com/StackMma/status/707745324543119361
Mar 10, 2016 at 1:00 comment added The Vee If you take the one before last step of Trace of either of the last two commands' evaluation, you get two objects which are identical to the last bit on every level but transform to True and False, respectively. So Uncompress@*Compress does not corrupt the object itself but some part of MMA's metadata about it that determines the result. This survives if you save the two objects in MX and import back (not WDX, that makes them both False just like the compression), so it's more than just runtime state of the kernel (evaluate cache etc.)
Mar 10, 2016 at 0:41 comment added The Vee Confirmed with "10.3.1 for Linux x86 (64-bit) (December 8, 2015)". Very strange indeed.
Mar 9, 2016 at 22:48 comment added Dr. belisarius Same with "9.0 for Microsoft Windows (32-bit) (January 24, 2013)"
Mar 9, 2016 at 22:41 history asked Vladimir Reshetnikov CC BY-SA 3.0