Lines Matching refs:in
3 This file lists standards that any programmer adding or changing code in
5 features are going in that general direction. Many sections have been
10 1. Document your code in source files and the manual. (tm)
12 1. PHP is implemented in C99. The optional fixed-width integers from
44 calculated with `strlen()`. Write your functions in such a way so that
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
61 code was commented out, especially in bundled libraries.
72 in debug mode.
78 may need to control or free the memory, or when the memory in question needs
88 1. Function names for user-level functions should be enclosed with in the
89 `PHP_FUNCTION()` macro. They should be in lowercase, with words underscore
119 included in the user function name, and should be clearly related to the
120 parent program or function family. This should be in the form of `parent_*`:
141 followed by a word or an underscore-delimited list of words, in lowercase
149 1. Variable names should be in lowercase. Use underscores to separate between
157 1. Class names should be descriptive nouns in *PascalCase* and as short as
158 possible. Each word in the class name should start with a capital letter,
228 `php_modulename_function()` to avoid symbol collision. They should be in
229 lowercase, with words underscore delimited. Exposed API must be defined in
236 Unexposed module function should be static and should not be defined in
257 variable declaration section and the statements in a block, as well as
258 between logical statement groups in a block. Maintain at least one empty
274 spaces. It is important to maintain consistency in indentation so that
296 include a file labeled `EXPERIMENTAL` in the function directory, and that the
313 aliases listed in the documentation for the parent function. For ease of
319 code can be reasonably be kept as part of the codebase. See the `README` in the
