Commenting out the offending line is the correct fix. This bug exists all the way back to AT&T sources. It is due to the routine being declared at the top of the shell script, but all of the functionalized code was not removed properly. I imagine it was never found because it is used so rarely, it never came up in testing.