Last modified: 2012-04-12 13:55:25 UTC
The doc comment above it doesn't conform to how it works.
It does say it returns boolean (at least in trunk). What did you want?
"by looking at wfMsg() output" doesn't match its current implementation (it was working in that way).
wfMsgEmpty is going to be deprecated in favour wfMessage()->exists().
I imagine it'll remain for quite some time...the wfMsg* functions have been around for ages and we can't get rid of them all at once. Fixed the docs in r87481.