Re: [drupal-devel] Why is there no designation between hooks and private functions in a module?

many modules in Drupal tend to name their private functions (eg non-hooks) as

function _mymodule_functionname()

Maybe enforce such a convention?

This does not need that huge patches inside core (but there are still many direct non-hook function calls from module to module)

Problem is that modules do have public API functions which are not hooks. Think about taxonomy module for example... So it is not "either hook or not public"... Goba