[squeak-dev] Why is ModificationForbidden not an Error?

Eliot Miranda eliot.miranda at gmail.com
Fri Apr 24 17:11:21 UTC 2020


> On Apr 24, 2020, at 9:55 AM, tim Rowledge <tim at rowledge.org> wrote:
> 
> 
>>> On 2020-04-24, at 3:10 AM, Marcel Taeumel <marcel.taeumel at hpi.de> wrote:
>>> 
>>> But this means the DB is now occupying the use of the readOnly bit, not available for other applications or use-cases.
>> 
>> Hmmm... ManagedObjects could be partitioned among multiple applications. For example, a game loading some save state could come across some read-only objects and then choses how to manage those. Another application could do this as well, not interfering with the first one. Both might be considered "small DB managers" so to say.
>> 
>> Of course, that check "myDomainObject isReadOnlyObject" would become standard procedure for such DBs, wouldn't it?
> 
> The fact that there is a helpful default handler for an exception does not (should not!) mean you can't catch it and do something more to your liking

+1. 

> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Design simplicity: It was developed on a shoe-string budget.
> 
> 
> 


More information about the Squeak-dev mailing list