> On Apr 5, 2016, at 12:56 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> 
> 
>> On 05.04.2016, at 20:04, tim Rowledge <tim at rowledge.org> wrote:
>> 
>> 
>>> On 05-04-2016, at 8:23 AM, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
>>> #releaseActionMap is part of the System package, not Kernel package, where
>>> Object belongs to.
>>> 
>>> Unless we decide to tightly couple both packages, we either require "self
>>> respondsTo:" or an override extension from System to Kernel.
>> 
>> Or we do a proper job of working out an effective way of doing this. I really hate to see (ab)use of #respondsTo:  like this. Surely it must be slower than simply sending the message - allowing the VM to do its normal fast lookups and caching - and occasionally having to catch a dNU: ?
>> 
>> If that is a practical path, then we need to imagine some simple and comprehensible ways to
>> a) catch the dNU and do.. whatever
>> b) discover that the catching is needed, which seems like some sneaky package analysis stuff well suited to a PhD student
>> c) find a way to use a & b without pissing off the general user/coder
> 
> 
> Or move #release to System?
> 
> I see no good reason to litter the code with unnecessary checks. It’s ugly, and if we ever untangled Kernel and System then I bet dependents stuff should not end up in Kernel, right?

+1

and then there's overrides...

> 
> - Bert -
> 
> 
> 
>