Passing undefined to catspeak_method with a Catspeak function, causes the self to be undefined and other to be the previous self upon calling. It should at the very least not change self/other in this matter. Though as it's unlikely someone will use undefined as the scope, I'd find this to be a low priority.
I've looked into this and it might be a more involved change than I'm thinking. It might have to wait until I can make more destructive changes in a potential v4 of Catspeak.
What version of Catspeak are you using?
3.1.0
What happened?
Passing
undefined
tocatspeak_method
with a Catspeak function, causes theself
to beundefined
andother
to be the previousself
upon calling. It should at the very least not changeself
/other
in this matter. Though as it's unlikely someone will useundefined
as the scope, I'd find this to be a low priority.