Hi--

	Faced with adapting a large amount of unmodularized behavior from a
kitchen-sink system to the Squat system (for another project), I
modified Object>>doesNotUnderstand: to "usurp" the message in question
in the Squat system. This installs a special method for the receiver
which, when run, fetches the real method from the kitchen-sink system,
then resends the message. All such added methods are recorded in a Squat
module.

	Since method transfer in Squat properly installs all method literals
(e.g., classes which are new to the target system), one may effectively
transfer all the behavior which is touched by the interpreter over some
arbitrary period of time. In particular, this seems like a convenient
way to create Squat modules from existing packages. One may then refine
the modules (break them up into multiple components with dependencies,
etc.).

	Of course, this means adapting Squat's remote message-sending framework
to the kitchen-sink snapshot, which I have done (currently, Squeak
3.6.5424, which is what the aforementioned other project is using).


	thanks,

-C

--
Craig Latta
improvisational musical informaticist
craig at netjam.org
www.netjam.org
[|] Proceed for Truth!