Require function prefixes for static and global functions

[Garados007]

Thomas requested this in byte-physics/igortest#327 (comment) but I need more clarification:

• Do we really want a function prefix for static functions as well? These are only accessible inside the module and therefore is no benefit using a function prefix. I support requiring a function prefix for global functions as they can clash with other user functions.
• How do we determine the name of the function prefix? There should be a rule.

Currently, function prefixes are only mentioned once in the coding convention and that is that they may be used before the name of a function.

[t-b]

Current proposal:

• Function prefixes are optional. If you use them for one function, all functions, regardless of static/threadsafe/etc. must have them. Constants and structures as well. Always restricted to one file.
• Globally accessible functions, e.g. part of the API, should always have a function prefix to avoid name collisions. Exceptions must be documented.
• If regular modules, i.e. #pragma moduleName=XXX, are used the following rules should be followed:
  • All module names start with the global prefix, i.e PREFIX_ModuleName
  • Function prefixes are the same as global prefixes
  • For very large projects, one can have multiple global prefixes.
• Prefixes for different projects should be different if possible. So try finding a unique global prefix.