I've started working on a module that relies on both the Services and CCK modules. I'm creating a web API for my company, and the underlying module has various support routines providing the interfaces for the external-to-drupal processing services.
As a part of creating the initial logic for the API, I gave the module and it's files the logical name 'companyNameAPI'.
Then, in our calls to the Services module logic, I defined a function to initialize the web API called 'companyNameAPI_init()'...
Testing the implementation through the Services browser worked fine, so I focused on the web API's code.
However, when simply browsing around my localhost R&D site, the 'companyNameAPI_init()' routine was getting called all the time... it took me a beat or two to realize that having a function with the name 'moduleName_init()' was an implementation of hook_init (http://api.drupal.org/api/function/hook_init/6). So my 'companyNameAPI_init()' was being called with every page render.
I fixed the situation by adding an underscore to every php function in the module that is not explicitly supposed to be a drupal hook.
Is there a function naming convention in common usage in situations like this?
What do you use for your internal-to-the-module support function naming convention?
