Possible function name clash with field_file_load()

I've discovered a little bug that triggers under certain conditions.

If there exists a module named 'field', the following code in function field_file.inc:field_file_load()

foreach (module_implements('file_load') as $module) {
  $function = $module .'_file_load';
  $function($file);
}

calls the function named 'field_file_load', which ends up in an infinite recursive loop.

The obvious solution is inserting the following test:

foreach (module_implements('file_load') as $module) {
  $function = $module .'_file_load';
  if ($function != 'field_file_load') {
    $function($file);
  }
}

which prevents unwanted recursive calls.

A simple test that allows this module to be deployed into any environment, even in the presence of a module named 'field'. Of course, function field_file_load() (if defined) in module 'field' won't be called by this code, but I think PHP would complain earlier anyway for the double function definition (the only solution is to rename the function).

BTW, this actually happened, it's not a made-up example. 'field' is not a great name for a locally developed module, granted, but the point still holds.