Lines Matching refs:of
38 meaningful names and can be easily manipulated. Any use of a numeric
43 holds the length property of each string, and that it shouldn't be
45 they'll take advantage of the length property, both for efficiency and in
54 1. Use `PHP_*` macros in the PHP source, and `ZEND_*` macros in the Zend part of
56 macros it gives a better understanding on what kind of macro you're calling.
60 where `FOO` is your git user `foo`. This allows easier tracking of why
64 missing a function, do not define the PHP version of the function, and do
66 use `function_exists()` to test for the existence of a function.
70 that ensures the deallocation of any unfreed memory at the end of a request.
77 The use of `malloc()` should be limited to cases where a third-party library
81 1. The return type of "is" or "has" style functions should be `bool`,
91 should not be used when they greatly decrease the readability of the
118 1. If they are part of a "parent set" of functions, that parent should be
120 parent program or function family. This should be in the form of `parent_*`:
122 A family of `foo` functions, for example:
141 followed by a word or an underscore-delimited list of words, in lowercase
154 count. The initial letter of the name is lowercase, and each letter that
176 name of the "parent set" (e.g. the name of the extension) if no namespaces
181 according to their standard notation. Usage of acronyms and initialisms is
215 1. Functions that are part of the external API should be named
239 that goes into the core of PHP or one of its standard modules, please
266 preprocessor directives you should put the `#` at the beginning of a line,
267 followed by any number of spaces.
269 1. The length of constant string literals should be calculated via ``strlen()``
270 instead of using ``sizeof()-1`` as it is clearer and any modern compiler
271 will optimize it away. Legacy usages of the latter style exists within the
283 of a new set of functions, it has been suggested that the first implementation
290 * Any authoring information (known bugs, future directions of the module).
301 aliases listed in the documentation for the parent function. For ease of
307 code can be reasonably be kept as part of the codebase. See the `README` in the
