Forcing MPS to produce error "unhandled exception XXX" for subclass of Expression

I'm developing low-level jdbc helper language. I have a concept JdbcQueryExpression which extends baseLanguage.Expression. This expression is then reduced to ClosureLiteral call { => }() .
How can I mark my JdbcQueryExpression as a call that produces SQLException?
4 comments
Yes, I've seen this thread, but in my case my concept is extended from Expression, not Statement, so I can't collect uncaught throwables using Statement.collectUncaughtMethodThrowables().
0
Sorry, my bad, I've missed your checking rule solution :)
0

Please sign in to leave a comment.