Alternatively, note that Henrik -- from the beginning -- provided us 
with a preference governing whether new-style (modular) 
class-definitions or old-style (category-based) class-definitions 
should be used.

The preference is called "modularClassDefinitions".

If you have modularClassDefinitions set to false, the 
class-definitions in fileouts you produce (and also the 
class-definitions you see in the browser) will be of the old 
pre-module format.

This provides an ideal way to get traditional Smalltalk class 
definitions into  fileouts, so that they can be read by older Squeaks 
and by non-Squeak Smalltalks.

   -- Scott


>  >Is there any easy way to file out a changeset from 3.3a and read it into
>>3.2gamma? I had trouble when I tried this since the format seems to have
>>changed.
>>    Ken
>
>The main issues here revolve around 3.3a's changes to the format of 
>class-definitions.  If a fileout produced in 3.3a happens to contain 
>any class definitions, they won't file in to 3.2gamma/external right 
>now.
>
>Fortunately, this problem has been solved -- Dan wrote some 
>compatibility methods for 3.2, which are already published to 
>3.2gamma/internal....