good catch , now we know why it does what it does. The reason why I did this is that there is an example method in OSCMessage that use this bad syntax in the comment.��
So it seems the Socket does send the message because Pharo does not perform a check on the argument, the Socket fails obviously but it may send the message to an unknown address. I think Supercollider watches for any kind of messages on various addresses and ports. At least that is only explanation I can think of.��
Or maybe I used the address string method and I forgot to mention it. Anyway thanks will keep this in mind.