Lines Matching refs:functions
33 2. Functions that are tightly integrated with other functions within the
44 4. When writing functions that deal with strings, be sure to remember
46 shouldn't be calculated with strlen(). Write your functions in such
67 8. Do not define functions that are not available. For instance, if a
74 counterparts. These functions implement an internal "safety-net"
89 1. Function names for user-level functions should be enclosed with in
110 2. If they are part of a "parent set" of functions, that parent should
115 A family of 'foo' functions, for example:
127 3. Function names used by user functions should be prefixed
213 line between two functions, preferably two. Always prefer::
275 implementation of a new set of functions, it has been suggested
277 in the function directory, and that the functions follow the
295 the parent function. For ease of reference, user-functions with
300 Backwards compatible functions and names should be maintained as long