Hi folks, in the C SDK, I'm hitting a bit of a funny issue. I've got object_method_typed working properly, and am sending messages to various objects after finding them via their scripting names. But I'm hitting some situations where the message crashes Max when it's a bad message. I'm hoping it's possible to have Max just spit out an error message in this situation instead of crashing. The scenario where I can make a crash happen every time is sending a message of "list 1.2 3.4" to a flonum object. This is invalid, but when I do this in a max patcher, either with a message box that says "list 1.1 2.2" or "1.1 2.2", the flonum happily takes the first number and there's no crash. Sending it via object_method_typed as message symbol "list", and array of atoms of 2 floats crashes. Using the same code to send this message to a zl.rev object is fine, so it seems like it works ok *when this is a valid message*. Is there some way of either capturing the error sans crash or checking first to see if this is a valid message for the target object?