If JSLint is run under Mozilla's JS interpreter, it will spew out
some warnings like 'function blah does not always return a value'.
Explicitly add some return statements to shut Mozilla up.
Silence warnings when run under Mozilla's JS interpreter
Figured not, but I'm curious why -- is there a reason that you don't consider implicit undefined returns an error that JSLint should check for?
You would not believe how much whining I hear. I only want JSLint to warn about stuff that can matter. I have not seen where default returns is a problem. If you can show me the evidence, I will change my mind.