My instances provide an organization for the classes in the system, just as a ClassOrganizer organizes the messages within a class. The only difference is the methods for fileIn/Out.

	remove
	categoriesMatching: removeCategoriesMatching: removeMissingClasses removeSystemCategory:

	fileIn/Out	top
	fileOut SystemOrganization fileOut
	fileOutCategory: Store on the file named category (a string) concatenated with '.st' all the classes associated with the category.
	fileOutCategory:asHtml: FileOut all the classes in the named system category.
	fileOutCategory:on: Store on the file associated with aFileStream, all the classes associated with the category and any requested shared pools.
	fileOutCategory:on:initializing: Store on the file associated with aFileStream, all the classes associated with the category and any requested shared pools.
	objectForDataStream: I am about to be written on an object file. Write a path to me in the other system instead.
	superclassOrder: Answer an OrderedCollection containing references to the classes in the category whose name is the argument, category (a string). The classes are ordered with superclasses first so they can be filed in.

	remove	top
	categoriesMatching: Return all matching categories
	removeCategoriesMatching: Remove all matching categories with their classes
	removeMissingClasses Remove any class names that are no longer in the Smalltalk dictionary. Used for cleaning up after garbage collecting user-generated classes.
	removeSystemCategory: remove all the classes associated with the category