I was checking the history of this change. This is the first one (besides commented-out codes), which must have been reused later (I haven’t seen it all yet). It was also kind of interesting to follow the changes and see variations
The OSCresponder bit, though, is removing the leading slash (not adding one if it wasn’t provided), and responding to both 
– whereas the thrust of this thread is in the opposite direction.
hjh
I wouldn’t read too much into this. I think it’s as simple as, nobody noticed – probably because SendReply examples in the help use slashes (which they should) and most users followed that model without thinking about it.
The case in this thread is certainly unexpected input (from SC’s perspective), possibly “incorrect usage.” (Then again, sendMsg doesn’t require the user to write the slash, so the OP wasn’t exactly wrong to think it wasn’t needed here.) Many many software packages have icky behaviors at these boundaries where something seems not obviously wrong but formally it’s not quite right. A fix to close the gap in SendReply is still appropriate but the fact that the gap was there at all doesn’t indicate a systemic problem.
In the company where I used to work, bug reports and feature requests had a “pain index,” calculated based on severity and customer demand, among other factors. This issue is not severe, and only one user has raised it in over a decade = very low pain index, not at all urgent. So I could ask why this is suddenly getting a couple dozen messages worth of scrutiny while more severe issues are not.
hjh
2 Likes