Lines Matching refs:function

18 -  In variable and function names use only lower case letters
72    -  Declare variables where needed (not all at function start).
81 Before every function prototype in ``.h`` files, include a Doxygen-formatted comment
152 The following is an illustration of an API function prototype with documentation
188   for calling the function.  Doxygen needs the blank line to separate "brief" from
191 - Describe function parameters with the ``@param`` command.  When a function writes
202 - Use back-quotes (\`...\`) around code elements (variables, type names, function names).  For type
203   names and function names, Doxygen generates a hyperlink to that code member's
206 - Append empty "()" to function names.  Doxygen will not generate a hyperlink to the
207   function's documentation without this.
241    documents ``name`` as a function parameter, and ``description`` is the text that
269 - In function arguments use ``type name[]`` declaration for array parameters instead of :cpp:expr:`…
272 - Widget members function must start with ``lv_<widget_name>`` and should receive :cpp:expr:`lv_obj…
276   function name as well (e.g. :cpp:expr:`lv_display_set_default(lv_display_t * disp)`)
283 …- Pass a pointer to a ``struct`` as the first argument of both the registration function and the c…
285 …- The last argument of the registration function must be ``void * user_data`` and the same ``user_…