Lines Matching refs:functions
32 2. Functions that are tightly integrated with other functions within the
43 4. When writing functions that deal with strings, be sure to remember
45 shouldn't be calculated with strlen(). Write your functions in such
66 8. Do not define functions that are not available. For instance, if a
73 counterparts. These functions implement an internal "safety-net"
88 1. Function names for user-level functions should be enclosed with in
109 2. If they are part of a "parent set" of functions, that parent should
114 A family of 'foo' functions, for example:
125 3. Function names used by user functions should be prefixed
211 line between two functions, preferably two. Always prefer::
273 implementation of a new set of functions, it has been suggested
275 in the function directory, and that the functions follow the
293 the parent function. For ease of reference, user-functions with
298 Backwards compatible functions and names should be maintained as long