Aside I have some general questions about OSCresponder: Despite the elegance of a lookup scheme using equality of OSCrespondres I have the general suspicion that the implementation of OSCresponder, creating on OSCresponder object per incoming message, could be an overhead for the garbage collector. Maybe a tree would be less overhead?
I've attached a version that is faster in lookup and should have less load on the garbage collector. Also when there is more responders it should be more efficient still, as it uses a signature (a Symbol) to do the match.
being a little less general, maybe that would be an improvement nevertheless. I still have to have a look how to do the OSCpathResponder with it.
Attachment:
%OSCresponder2.rtf
Description: application/applefile
Attachment:
OSCresponder2.rtf
Description: Binary data
Attachment:
%OSCresponder2.sc
Description: application/applefile
Attachment:
OSCresponder2.sc
Description: Binary data
-- .