Hello,
I'm currently looking at the use of the PackageOrganizerCache in Moose. There was some work in pharo about a new, more performant, better-structured (I think it's the idea ? :)) 'Package system' called RPackage. So before doing anything, I would like to know more about the use of PackageOrganizerCache: - Why do we use a cache ? I guess this is because accessing directly parent packages of specific classes or methods was to slow using the current package system. - If this is the good answer :), why was it too long? could another package system (RPackage) solve this problem and avoid us to use a cache ? - For which kind of task is used the packageCache in Moose? I saw that it was used at the import of smalltalk code, to link classes and method to their parent package, is that all ?
I do not really know. But this is an important issue. I experienced some problem when I modify some class extension in Smalltalk, then got some problem when loading back in Moose.
Cheers, Alexandre
On 27 Oct 2010, at 11:27, Cyrille Delaunay wrote:
Hello,
I'm currently looking at the use of the PackageOrganizerCache in Moose. There was some work in pharo about a new, more performant, better-structured (I think it's the idea ? :)) 'Package system' called RPackage. So before doing anything, I would like to know more about the use of PackageOrganizerCache:
- Why do we use a cache ? I guess this is because accessing directly parent packages of specific classes or methods was to slow using the current package system.
- If this is the good answer :), why was it too long? could another package system (RPackage) solve this problem and avoid us to use a cache ?
- For which kind of task is used the packageCache in Moose? I saw that it was used at the import of smalltalk code, to link classes and method to their parent package, is that all ?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Cyrille Delaunay