Yes. I have no problem to have a good names. The problem is that if we 
want to only have one class to deal with modules, vmparameter, 
garbageCollection...Then sources does not fit well.

That's why I asked before if we should have several classes (VMSUpport, 
Sources, ObjectMemory)
But I agree that for now having 2 or 3 classes is not good for now.

Here are the current methods this class Image has:

a Set(#snapshotPrimitive #processStartUpList: #removeFromShutDownList: 
#installLowSpaceWatcher #systemInformationString #bytesLeftString 
#shutDownSound #lowSpaceWatcherProcess #saveImageInFileNamed: 
#imageName: #memoryHogs #saveAsNewVersion #processShutDownList: 
#closeSourceFiles #okayToProceedEvenIfSpaceIsLow #version 
#add:toList:after: #saveAs #snapshot:andQuit: 
#snapshotEmbeddedPrimitive #primitiveGarbageCollect #externalizeSources 
#addToStartUpList:after: #currentChangeSetString 
#send:toClassesNamedIn:with: #endianness #fullNameForImageNamed: 
#garbageCollect #imagePath #saveImageSegments 
#writeRecentCharacters:toFileNamed: #primSignalAtBytesLeft: 
#setPlatformPreferences #addToStartUpList: #lastUpdateString 
#aboutThisSystem #logChange: #setGCParameters #signalLowSpace 
#bytesLeft #timeStamp: #internalizeChangeLog #garbageCollectMost 
#useUpMemoryWithContexts #saveChangesInFileNamed: #openSourceFiles 
#addToShutDownList: #useUpMemory #copyright #lowSpaceThreshold 
#useUpMemoryWithTinyObjects #forceChangesToDisk #primBytesLeft 
#createStackOverflow #useUpMemoryWithArrays #isBigEndian #vmPath 
#snapshot:andQuit:embedded: #unbindExternalPrimitives 
#addToShutDownList:after: #quitPrimitive #changesName 
#internalizeSources #recover: #assureStartupStampLogged 
#lastQuitLogPosition #bytesLeft: #imageName #isLittleEndian 
#saveAsEmbeddedImage #removeFromStartUpList: #changeImageNameTo: 
#fullNameForChangesNamed: #lowSpaceWatcher #primLowSpaceSemaphore: 
#writeRecentToFile #shutDown #datedVersion #saveSession)


The methods related to vmParameters and special objects are missing.

Stef




On Thursday, June 12, 2003, at 01:50 PM, Bert Freudenberg wrote:

>
> Am Mittwoch, 11.06.03 um 23:43 Uhr schrieb Stephane Ducasse:
>
>>>> Come one andreas
>>>>
>>>> 	Image abandoneSources
>>
>>
>> Ok call it ImageVMSupport this is already better than 
>> SystemDictionary which is a namespace.
>>
>> RuntimeImageSupport is much cooler but now people will complain this 
>> is too long to type.........
>
> Isn't something like SourceManagement more appropriate? Or just 
> Sources? That class could become a home for all source-related stuff. 
> "Concepts", like Andreas pointed out ;-)
>
> -- Bert
>
>