17 May
2009
17 May
'09
7:56 p.m.
Dear list
With the latest Moose update, it is now possible to load Pharo into
Moose in less than a minute.
However, after loading Moose, you need to run PackageOrganizerCache
buildSystemCache (it takes less than 2 minutes to run).
Not sure if I really want to store this cache in MC for the moment
--
Simon
19 May
19 May
12:05 p.m.
With the latest Moose update, it is now possible to
load Pharo into
Moose in less than a minute.
However, after loading Moose, you need to run PackageOrganizerCache
buildSystemCache (it takes less than 2 minutes to run).
Not sure if I really want to store this cache in MC for the moment
What happens if one forget to do so?
Why the cache is not build on demand?
We should talk about this.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
1:54 p.m.
On 19 mai 09, at 12:05, Alexandre Bergel wrote:
Importer will not complain, but all classes will appear in
'Unpackaged' packages, and it takes more time because my code is buggy
in this area
With the
latest Moose update, it is now possible to load Pharo into
Moose in less than a minute.
However, after loading Moose, you need to run PackageOrganizerCache
buildSystemCache (it takes less than 2 minutes to run).
Not sure if I really want to store this cache in MC for the moment
What happens if one forget to do so? Why the cache is not build on demand?
Because this is a workaround and I didnt want to think too much about
it. This is more of a Pharo issue with the lack of first-class packages.
We should talk about this.
--
Simon
2:02 p.m.
We should seat down together.
Alexandre
On 19 May 2009, at 13:54, Simon Denier wrote:
On 19 mai 09, at 12:05, Alexandre Bergel wrote:
Importer will not complain, but all classes will appear in
'Unpackaged' packages, and it takes more time because my code is
buggy in this area
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
With the
latest Moose update, it is now possible to load Pharo
into Moose in less than a minute.
However, after loading Moose, you need to run
PackageOrganizerCache buildSystemCache (it takes less than 2
minutes to run).
Not sure if I really want to store this cache in MC for the moment
What happens if one forget to do so? Why the cache is not build on demand?
Because this is a workaround and I didnt want to think too much
about it. This is more of a Pharo issue with the lack of first-class
packages.
We should talk about this.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5695
days inactive
5697
days old
3 comments
2 participants
participants (2)
-
Alexandre Bergel -
Simon Denier