Hi Thierry, On Thu, Dec 4, 2014 at 2:31 PM, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Hi all,
I'm just wondering.
Would it work to have a package format based on Fuel?
It doesn't have to be based on Fuel. Monticello .mcz's are just zips that contain any number of files: Archive: trunkpackages/Kernel.spur-eem.866.mcz Length Date Time Name -------- ---- ---- ---- 15 08-07-14 09:12 package 294780 08-07-14 09:12 version 1370995 08-07-14 09:12 snapshot/source.st 1442870 08-07-14 09:12 snapshot.bin -------- ------- 3108660 4 files Right now package and version are juts textual, and you've been complaining about the parsing speed. It would be easy to extend the package to include e.g. version.fuel. It is also a huge advantage to keep both the .bin (a not-as-fast binary loading format similar in use to Fuel but more primitive) along side the source code, because the source can be extracted without a running system, and can be compiled if, for some reason, binary loading fails. So instead of changing the format you could simply augment it with a snapshot.fuel, modifying the writer to include it, and modify the reader to use the .fuel if it exists. Would that make loading faster?
Yes. But not hugely because the .bin already loads faster than the .st. You might do some profiling?
Does it already exist?
Much of what you need is there. Use the Pharo, Luke.
Thanks,
Thierry
-- best, Eliot