On 09-02-2014, at 2:56 PM, Frank Shearar <frank.shearar at gmail.com> wrote:

> On 9 February 2014 22:22, tim Rowledge <tim at rowledge.org> wrote:
>> 
>> On 09-02-2014, at 2:19 PM, Frank Shearar <frank.shearar at gmail.com> wrote:
>>> So despite the #respondsTo: guard, a ByteString still gets into the
>>> second block. Thoughts?
>> 
>> Well you *are* testing ‘ref’ rather than ‘key’.
> 
> Eh? It's "ref respondsTo: #costume" and then "ref costume”.

Sorry -  miscounted blocks. I saw  [ References removeKey: key ] as the second one… thought you were checking ref and then using key. Getting a ‘true’ from the respondsTo: and then a dNU: is more than a bit worrying.

I’m always a bit worried when  I see code iterating across a collection that includes removing something from that collection. Can’t quite see how that would affect your code though.

References is empty in my image so I can’t really examine anything for class. Looks to me like only Players ought to be in there so a ByteString seems like evidence of some interesting bug. 

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: ED: Eject Disk