Lines Matching refs:function

29 - If you break a function declaration over multiple lines, do it like this:
154 - Typically, function parameters fit into three categories: input parameters,
157   indicate they are input-only and not changed by the function. Return
210   lists at the top of the function.
213   almost always be declared as the last variable at the top of the function.
235 - Do not mix multiple variable definitions with function invocations or
257   to the end of a function, and little else. Never jump backwards!
337   Be strict with this. When you write a function that can fail due to more than
394   When returning from a `void` function, you may also want to shorten the error
395   path boilerplate by returning a function invocation cast to `(void)` like so:
402   Don't cast function calls to `(void)` that return no error
412 - For every function you add, think about whether it is a "logging" function or
413   a "non-logging" function. "Logging" functions do (non-debug) logging on their
417   function calls a "non-logging" function, it should log about the resulting
418   errors. If a "logging" function calls another "logging" function, then it
433   the called function, use `SYNTHETIC_ERRNO` wrapper to tell the logging
468   `alloca_safe()` within a loop or within function call
469   parameters. `alloca_safe()` memory is released at the end of a function, and
473   Regarding not using `alloca_safe()` within function parameters, see the BUGS
605 - When exposing public C APIs, be careful what function parameters you make
607   be `const`, even if you are writing an otherwise read-only accessor function
656   long lines. Use `read_line()` instead, which is our own function that handles
661   to exit from the main function of a process. If you `fork()`ed off a child