[interfacekit] Re: BLooper::SetCommonFilterList() mod

OK, now I'm getting nit-picky. ;P  I think I should check for ownership 
issues *before* nuking the local list, thus leaving the original filter 
list intact.  Can anyone think why it should be done *after*?

Thanks,

e

>
>>>From the BeBook:
>>>>The BLooper takes ownership of all objects in filters, as well as 
>filters itself. 
>>If filters is NULL, the current list is deleted without a replacement. 

>>CommonFilterList() returns a pointer to the current list. You can 
>examine 
>>the list but you shouldn't modify or delete it. 
>>
>>This clearly indicated that a filter list can only be used with one 
>looper.
>
>Yes, there is no doubt in my mind about that.
>
>>> Anyone see any problem with this?
>>No, would be ok for me. Except that there may be programs
>>already doing it, but since they will crash anyway, just add
>>the check.
>
>Agreed.  If anything, it will make it easier to debug those programs.  
>I'm going to initially implement to check every list element; if it 
>proves to be an issue later, I'll try to short cut it somehow.

Necessity is the plea for every infringement of human freedom. It is the 
argument of tyrants; it is the creed of slaves.
        -William Pitt, British prime-minister (1759-1806)

Other related posts: