Szabolcs has asked WRI support about mx files, in particular:
- Can we expect that MX files written by Mathematica 10.0.0 will be readable by future point released such as 10.0.1 or 10.0.2?
WRI: Yes.
Source: an e-mail and the topic.
And this is true, in V10.3 I can open .mx files generated in V10.2. However, I can't open files from 10.3 in 10.2, getting an error:
DumpGet::bgnew : File ***.mx has been written by a newer version of DumpSave and cannot be loaded.
Why this matters?
Well, Cloud $VersionNumber
is still 10.2
... so I can't work on my desktop 10.3 with projects that involve cloud interactions with mx files. Or I have to create work arounds from my current setup. Like using 10.2 from time to time or Cloud side DumpSave
.
To fit the MMA.SE scheme, let me ask the question. Can I DumpSave
from 10.3 so that it is readable on Clound and/or 10.3 desktop MMA?
Export[..., Compress[expr], "String"]
in place of MX. ThenUncompress@Import[..., "String"]
. Usually it's fast enough and much faster than WDX. BTW did I put that in the pastebin? $\endgroup$ – Szabolcs Oct 19 '15 at 10:04Export
-like, i.e. data exchange, or is itDumpSave
-like, i.e. save a session with all of its variables/function definitions, and then restore it later? BTW Export works with MX and doesn't require the exported data to be assigned to variables. $\endgroup$ – Szabolcs Oct 19 '15 at 12:12