[squeak-dev] Securing access to the .changes file
tim Rowledge
tim at rowledge.org
Wed Apr 19 20:59:27 UTC 2017
> On 18-04-2017, at 11:26 AM, tim Rowledge <tim at rowledge.org> wrote:
>
> As a minimal fix I think we could solve this by
> a) add #hasWriteableChanges to SourceFileArray, default returning false.
> b) add ditto to each of the current subclasses, returning whether the file at 2 is not nil
> c) extend at least ClassDescription>acceptsLoggingOfCompiliation to ^SourceFiles hasWriteableChanges, with the other implementors of #acceptsLoggingOfCompiliation being a bit less obvious to me.
I’ve submitted an exemplar set of changes to the inbox since I do not know what we ought to do with classes such as UnscriptedPlayer. See inbox/Files-tpr.169 & Kernel-tpr.1075
tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: TVO: Type Various Obscenities
More information about the Squeak-dev
mailing list
|