Lines Matching refs:as
18 …ent cannot cover every situation, so the following general guidelines should be used as a fallback:
72 In DPDK sources, the include files should be ordered as following:
142 as it increases the number of target binaries that need to be built and tested.
150 then regular C conditionals, as described in the next section,
154 then conditional compilation should be used, as described in this section.
171 * In the comments, the subexpression ``defined(FOO)`` is abbreviated as "FOO".
172 For the purposes of comments, ``#ifndef FOO`` is treated as ``#if !defined(FOO)``.
214 /* report a unit tests as unsupported on Windows */
255 The developer should group bitfields that are included in the same integer, as follows:
295 Ordering by size then ensures that as little padding is added to the structure as possible.
298 * Try to make the structure readable by aligning the member names using spaces as shown below.
317 Uses of ``bool`` in structures are not preferred as is wastes space and
318 it's also not clear as to what type size the bool is. A preferred use of
319 ``bool`` is mainly as a return type from functions that return true/false,
365 with an existing (as of 2020) hardware or protocol
397 for example, you need to know if the typedef is the structure itself, as shown above, or a pointer …
398 …red exactly once, whereas an incomplete structure type can be mentioned as many times as necessary.
404 For example, ``#define pint int *`` does not work as expected, while ``typedef int *pint`` does wor…
408 Avoid typedefs ending in ``_t``, except as specified in Standard C or by POSIX.
413 This is especially true when the function type is used as a parameter to another function.
443 …to prevent confusion as to whether the second line of the control statement forms part of the stat…
453 var3 == var4){ /* confusing to read as */
508 * Closing and opening braces go on the same line as the else keyword.
551 * Avoid obvious comments such as
608 …The second and subsequent lines should be further indented as for line statement continuations as …
638 …&R) function declaration should not be used, use ANSI function declarations instead as shown below.
639 * Long argument lists should be wrapped as described above in the function prototypes section.
683 * Functions which work on bursts of packets, such as RX-like or TX-like functions, should return th…
690 …(Typecasting can prevent the compiler from warning about missing prototypes as any implicit defini…
695 The above rule about not typecasting ``void *`` applies to malloc, as well as to DPDK functions.
735 …They are expanded as a compiler builtin and allow the developer to indicate if the branch is likel…
752 …local to a file must be declared as ``static`` because it can often help the compiler to do some o…
753 * Functions that should be inlined should to be declared as ``static inline`` and can be defined in…
756 …Static functions defined in a header file must be declared as ``static inline`` in order to preven…
761 The ``const`` attribute should be used as often as possible when a variable is read-only.
767 Input and output operands should be named to avoid confusion, as shown in the following example:
806 In general, the naming scheme is as follows: ``type.section.name``
833 Each PMD, library or component can create as many specializations as required.
863 In order to catch possible issues as soon as possible,
887 itself, for example, that the library name is the same as the directory name in
925 dependencies should be specified as strings, each one giving the name of
940 returned as dependency objects, as returned from the meson
972 for all needed include files as part of a DPDK build when
995 map file, as part of the build process, so if the directory name and
1002 objects that were compiled up as part of another target given in the
1022 For drivers, the values are largely the same as for libraries. The variables
1102 …In this case, the opening and closing braces of the list must be on the same line as the list item…
1109 at the same level as the opening braced statement.