yes.
note that reliance on these backstop methods is dispersed all over the system,
starting with the browsers, ranging over the compiler and not ending in  monticello.
this will be an intense task.

-- 
Tobias Pape
sent from a mobile device

> Am 26.01.2014 um 12:16 schrieb Frank Shearar <frank.shearar at gmail.com>:
> 
>> On 25 January 2014 22:55,  <commits at source.squeak.org> wrote:
>> Tobias Pape uploaded a new version of Kernel to project The Trunk:
>> http://source.squeak.org/trunk/Kernel-topa.834.mcz
>> 
>> ==================== Summary ====================
>> 
>> Name: Kernel-topa.834
>> Author: topa
>> Time: 25 January 2014, 11:55:18.392 pm
>> UUID: 0184b773-5c2a-40a9-9922-3b1ba2443767
>> Ancestors: Kernel-topa.833
>> 
>> Move trait-backstops back to Kernel, so trait unloading still works.
>> 
>> My previous change is now unecessary.
>> 
>> =============== Diff against Kernel-topa.833 ===============
> 
> This means that in an image with unloaded Traits we'd still have those
> backstops in Kernel, right? At some stage I'd like to see that not
> happen. We can take another run at the problem in 4.6.
> 
> frank
>