Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!usc!snorkelwacker!ira.uka.de!fauern!tub!db0tui11!muhrth
From: MUHRTH@tubvm.cs.tu-berlin.de (Thomas Muhr)
Newsgroups: comp.lang.smalltalk
Subject: Getting rid of the development environment?
Message-ID: <90228.105114MUHRTH@DB0TUI11.BITNET>
Date: 16 Aug 90 08:51:14 GMT
Organization: Technical University Berlin
Lines: 15

After completing an application, an image is a mixture of development
oriented parts and parts needed by the application. The former occupies
the larger fraction, I guess. Are there any easy ways to check for those
classes/methods/objects which are not addressed by an application and can
therefore be removed? Best way would be an automatic solution which is
not trivial: All application procedures have to be simulated, crossreferences
have to be established. The cloning mechanisms in ST V need the explicit
mentioning of the classes/methods to be removed.
Any help is welcome -
Thomas
-------
Thomas Muhr, Technical University of Berlin, BITNET: muhrth@db0tui11
   Project ATLAS - Computer Based Tools for Qualitative Research
         "Computers, like every technology, are a vehicle
      for the transformation of tradition." (WINOGRAD/FLORES)