A simple approach to handling an absence of a writeable changes file when compiling code changes.
NB - this does NOTNOTNOT address the other implementors of #acceptsLoggingOfCompilation such as UnscriptedPlayer etc that do ... odd things.
This set of changes must of course be paired with Files-tpr.169 wherein lies the new code to test for a changes file
=============== Diff against Kernel-eem.1074 ===============
Item was changed:
----- Method: ClassDescription>>acceptsLoggingOfCompilation (in category 'compiling') -----
"weird name is so that it will come lexically before #compile, so that a clean build can make it through. 7/7/96 sw"