Functions definitions in /etc/profile.d/00functions.sh use this syntax:

 function name () {
  commands
  }

Users who select /bin/ksh as their login shell (which is actually pdksh)
get an error, the function remains undefined, and later calls to that
function come up "not found," because in pdksh function definitions have
one of these two syntaxes (one to get the behavior of AT&T ksh, one to
get that specified under POSIX):

 function name {
  commands
  }

or

 name() {
  commands
  }

It's not permitted to use both the word "function" and the empty paren-
theses.

Meanwhile, /etc/profile.d/mc.sh defines a function with only the empty
parentheses, omitting the word "function," and it's fine under both bash
and pdksh.  The bash man page implies that the word "function" is totally
optional; if it were omitted in /etc/profile.d/00functions.sh, there would
be no harm under bash and much gained for ksh users.

[Hope I'm filing this report properly.]