You're right, there are many ways to break something like this, but I was just thinking of something for the common case: sub foo appears, but a call to foo(...) doesn't appear in the same package. That's what I was trying to say with "it doesn't have to be bulletproof".

I guess an analogy would be perltidy. It can be thrown off without trying very hard, but in the common cases it can be helpful.