Lines Matching refs:example

8 concrete realization of an abstract base class. For example,
17     of which is capitalized, for example, `KSPSolve()` and
22     underscore between each word. For example, `MAT_FINAL_ASSEMBLY`.
27     - have an appended `_Private` (for example, `StashValues_Private`)
29     - have an appended `_Subtype` (for example, `MatMultSeq_AIJ`).
35 04. Function names in structures (for example, `_matops`) are the same
37     in lowercase. For example, `MatMultTranspose()` has a
42     example, `KSPSolve_GMRES()`.
45     object, followed by any subclass name, for example,
50     functions end with `Default` (for example, `PetscSignalHandlerDefault()`).
54     the word “set” or “get”, for example, `-ksp_gmres_restart`.
56 09. Specific `XXXType` values (for example, `MATSEQAIJ`) do not have
58     an underscore, for example, `MATSOLVERSUPERLU_DIST`.
60 10. Typedefs for functions should end in `Fn` as in, for example, `SNESFunctionFn`.
133 02. All local variables of a particular type (for example, `PetscInt`) should be listed
211 …rnal()` or its variants that are specialized for particular packages, for example `PetscCallBLAS()`
240     scope, it is encouraged to declare them in that scope. For example:
283 16. Developers can use // to split very long lines when it improves code readability. For example
320     each function call. See, for example, `DMDAVecGetArray()`.
332     lines in the header. For example, do
384     See `PetscDefined()` for an example of how to work around MSVC's limitations to write
419     `PetscFunctionReturn()` For example
437     For example, use:
473     always use `PetscMallocN()` (for example, `PetscMalloc1()`),
480     that works if the MPI feature is not available; for example,
491     functionality as an available MPI routine. For example, do not write
507     example
526     For example,
560     such as `PetscPrintf`, must be cast to `double`, for example,
600 > /* SUBMANSEC = submansec (for example Sys) */
672     information about the code for developers, for example, why a
693 2. Avoid double spaces in makefile rules. For example `"cat file | tr ..."` not `"cat  file   |  tr…
695 3. Single space after `";"` but not before it. For example `"make ex1; make ex2"` not `"make ex1 ;m…
702 3. Company names and terms that are traditionally all capitalized, for example, MATLAB, NVIDIA, and…