Exactly. I was discussing here this morning and we will do that. Move 
everything
in one class so it confirms my intuition because with the other solution
the decomposition started to be ad-hoc what is VM support and what is 
Image was not clear.

Thanks for the feedback this is excatly the kind of remark I was 
looking for.
Stef

On Monday, June 9, 2003, at 11:15 PM, Tim Rowledge wrote:

> Stephane Ducasse <ducasse at iam.unibe.ch> wrote:
>
>>> I would like to continue cleaning systemDictionary.
>>> I would like to move away from SystemDictionary
>>>
>>> - 'memory space' methods
>>> 	- I was thinking to create a MemorySpace class
>>> - vm related information (listModule, vmParamAt...)
>>> 	- into VMSupport
>>>
>>> - 'snapshot and quit' + 'image, changes name' + condense changes ->
>>> 	- into Image
>>
> I think a simpler move might be to have a SystemInfo class to hold all
> the vm/memory/platform related info. Factoring is good but it is
> possible to go too far.
>
> tim
> --
> Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
> Oxymorons: Passive aggression
>