Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!ames!haven!mimsy!mojo!news
From: tpermutt@eng.umd.edu (Thomas Permutt)
Newsgroups: comp.lang.smalltalk
Subject: compressChanges (Smalltalk/V)
Message-ID: <1991Feb5.202908.3106@eng.umd.edu>
Date: 5 Feb 91 20:29:08 GMT
Sender: news@eng.umd.edu (C-News)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 14

Why does compressChanges remove class definitions from the change log?
More importantly, how do people work around this?

It seems to me that the change log contains three kinds of information needed
to restore, say, a crashed system:  methods, assignments to global and pool
variables, and definitions of new or modified classes.  Methods are kept by
compressChanges.  Essential global assignments tend to be few, and a lot of
the garbage that should get compressed out consists of inessential global
assignments, so I am willing to keep track of these myself:  I can always
define a method setAllGlobals to preserve a record of these in the change
log if I want.  But what am I supposed to do about class definitions?
Look through the change log and write them all down before compressing?
Modify the subclass: method to make a separate log of them?  Seems like it
ought to be more automatic.  Am I missing something?