2.x fileout may version classes in 3.x filein
Fileout of the contents of a SymbolDictionary, using GBS or directly by
ClassOrganizer >> fileOutClassesAndMethodsInDictionary:on:
creates a fileout that is poorly structured. When filed in again, this
will cause the classes to be versioned, circumventing recent changes that
avoid unneccessarily versioning classes.
This is a particular problem when performing file-in as part of a GemStone/S
64 Bit upgrade to 3.0 or later. If the filein versions the classes, the
unconverted classes and methods will remain in the image.
Fileouts of individual classes are not affected.
You can recompile methods directly after conversion, rather than filing
in code. Filing out the 2.x code as classes avoids the problem.