Hi Martin, It's interesting idea - to have separate Fuel packages for serialization and materialization (and probably some common base). Currently it is not the most important task to do (we need to clean the residues of the Compiler in the image etc.) but I like it :-) -- Pavel On Mon, Apr 9, 2012 at 6:21 AM, Martin Dias <tinchodias@gmail.com> wrote:

Nice! I guess fuel needs for materialization only 50% of its methods and 2/3 of its classes. In a future I can work on that if you think it's worthwhile.

Martín

On Sun, Apr 8, 2012 at 1:59 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:

...

Simply gorgeous!

On Apr 8, 2012, at 6:23 PM, Pavel Krivanek wrote:

...

Hi,

I created an experimental CI build that loads Fuel into the Pharo Kernel, unloads Compiler and uses an special launcher that expects a binary package name as command line argument.

https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Fuel/

You can test it with something like (see attachment):

CogVM PharoKernel-Fuel-1.4.image testingPackage.fuel

Following code exports a fuel binary package from the image:

FileStream forceNewFileNamed: 'testingPackage.fuel' do: [:aStream |       aStream binary.       FLPackageStore new storeOn: aStream packageNamed: 'TestingPackage'.].

As you can see from the output of the testing class, there is no Compiler class in the image.

Cheers, -- Pavel <testingClassOutput.txt><TestingPackage.st><testingPackage.fuel>