Searched full:comment (Results 1 – 8 of 8) sorted by relevance
| /libCEED/ |
| H A D | .codecov.yml | 12 comment: false
|
| H A D | CONTRIBUTING.md | 20 …User <helpful@example.com>` or [`Co-authored-by: Snippet Mentor <code.by@comment.com>`](https://he…
|
| H A D | Doxyfile | 6 # All text after a double hash (##) is considered a comment and is placed in 9 # All text after a single hash (#) is considered a comment and will be ignored. 206 # first line (until the first dot) of a Javadoc-style comment as the brief 217 # as being the beginning of a Javadoc-style comment "banner". If set to NO, the 225 # line (until the first dot) of a Qt-style comment as the brief description. If 233 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as 235 # to treat a multi-line C++ comment block as a detailed description. Set this 952 # comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f18, *.f, *.for, *.vhd, 1133 # characters from position 72 are to be considered as comment. A common 1134 # extension is to allow longer lines before the automatic comment starts. The [all …]
|
| H A D | README.md | 396 …ailing [ceed-users@llnl.gov](mailto:ceed-users@llnl.gov) or by leaving a comment in the [issue tra…
|
| /libCEED/benchmarks/ |
| H A D | postprocess_plot.py | 17 x_range = (1e1, 4e6) # plot range for the x-axis; comment out for auto 18 y_range = (0, 2e9) # plot range for the y-axis; comment out for auto
|
| /libCEED/backends/magma/ |
| H A D | ceed-magma.h | 89 // Comment the line below to use the default magma_is_devptr function
|
| /libCEED/doc/sphinx/source/ |
| H A D | CONTRIBUTING.md | 20 …User <helpful@example.com>` or [`Co-authored-by: Snippet Mentor <code.by@comment.com>`](https://he…
|
| H A D | libCEEDdev.md | 154 For example, the comment 236 8. All libCEED functions must use Doxygen comment blocks before their *definition* (not declaration…
|