Re: .st file naming

On Tue, Apr 07, 2015 at 05:28:14PM +0100, Jan Vrany wrote:

> But then the package to which certain code element belongs would 
> depend on in which order you load packages. Very bad IMO. 
> Alternatively, you may have it as prerequisite of every package, 
> but that's bit silly :-) 

Well, if you run VisualGST.. you will load it first. When I
run my deployment image.. I don't load it as size and performance
matters (I deploy on a ARM7TDMI system..)


> 
> > The benefit of a registry is that
> > depending on your storage structure you don't need to walk all
> > classes/compiled methods to find the ones that belong to a package.
> > 
> True. But how often one need to do that? When you commit or when
> one want to display code that belongs to a package. Both are not
> performance-critical operations and walking through all classes is
> fast enough. 
> 
> Anyway, having this feature in kernel or in external package is 
> orthogonal to external data structure or reference from class(info) and 
> method(info)
> 
> There's one more complication to keep in mind, independent of above. 
> overwrites have to be handled too. A method has to keep the overwritten
> method. Again, one can keep it in MethodInfo...

Okay, true. 

> Yes. Paolo? 

I care about memory increase of a plain kernel/image as well. How
much time do you have for GNU Smalltalk?