HomeSort by: relevance | last modified time | path
    Searched refs:comments (Results 1 - 25 of 31) sorted by relevancy

1 2

  /src/tests/usr.bin/indent/
opt_bad.c 92 comments(void) function in typeref:typename:void
103 comments(void) function in typeref:typename:void
opt_bl_br.c 132 * Test multiple mixed comments after 'if (expr)'.
182 comments(void) function in typeref:typename:void
208 comments(void) function in typeref:typename:void
241 comments(void) function in typeref:typename:void
t_options.lua 51 -- Inside the input..end or run..end sections, comments that start with '$'
68 local section_excl_comm = "" -- without dollar comments
69 local section_incl_comm = "" -- with dollar comments
278 -- Hide comments starting with dollar from indent; they are used for
t_misc.sh 240 * It is possible to embed comments in the middle of an option, but nobody
302 # means that all kinds of comments are effectively ignored. When a
306 # words can be used for comments.
308 /* Comments are effectively ignored since they never match. */
  /src/usr.bin/make/unit-tests/
comment.mk 3 # Demonstrate how comments are written in makefiles.
15 # Comments can be indented with spaces, but that is rather unusual.
17 # Comments can be indented with a tab.
19 # they are just makefile comments. Before that commit, these comments
22 .if 1 # There can be comments after conditions.
check-expect.lua 8 Check that the various 'expect' comments in the .mk files produce the
23 Search the following "expect:" and "expect[+-]offset:" comments
directive-include-guard.exp 9 Parse_PushInput: comments.tmp:1
10 Skipping 'comments.tmp' because 'COMMENTS' is defined
char-005c-reverse-solidus.mk 14 # TODO: escape '#' in comments
varmod-defined.mk 84 # can be used to add comments in the middle of an expression. That
cond-token-plain.mk 32 # comment handling anymore. The comments are supposed to be stripped off
38 # comments are stripped in an earlier phase. See "case '#'" in
directive-for-empty.mk 72 # In comments like 'empty(i)', the text must be preserved as well.
directive-include-guard.mk 69 # Comments and empty lines do not affect the multiple-inclusion guard.
70 CASES+= comments
71 LINES.comments= \
74 '.ifndef COMMENTS' \
76 'COMMENTS=\#comment' \
79 # expect: Parse_PushInput: comments.tmp:1
80 # expect: Skipping 'comments.tmp' because 'COMMENTS' is defined
  /src/usr.bin/indent/
README.md 13 In 2021, indent was updated to handle C99 comments and the code got a major
  /src/lib/libc/time/
checktab.awk 113 comments = $4
121 tz2comments[tz] = comments
Makefile 535 # this is so that comments can contain non-ASCII characters.
741 # Awk script to extract a Git-style author from leap-seconds.list comments.
749 /Questions or comments to:/ { author_line = 1 } \
  /src/usr.bin/xlint/lint2/
check-msgs.lua 8 Check that the message text in the comments of the C source code matches the
  /src/distrib/notes/common/
extract-contrib-string.pl 112 $comments = !$html && !$xml;
280 if ($comments) {
  /src/sys/external/gpl2/dts/dist/arch/arm64/boot/dts/allwinner/
sun50i-h6-orangepi-lite2.dts 53 * See the comments for CLDO2.
  /src/lib/
checkver 83 For more information, read the comments.
  /src/sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/scripts/
check_lint.sh 20 COMMON_LINT_FILTER=-build/include,-build/header_guard,-legal/copyright,-whitespace/comments,-readability/casting,\
cpplint.py 210 'whitespace/comments',
320 # False positives include C-style multi-line comments (http://go/nsiut )
363 Parses any NOLINT comments on the current line, updating the global
369 raw_line: str, the line of input text, with comments.
860 "cpplint(category)" comments on the offending line. These are
894 # Matches multi-line C++ comments.
896 # have to take care of space removals tools so we can handle comments inside
912 This function does not consider single-line nor multi-line comments.
947 """Clears a range of lines for multi-line comments."""
948 # Having // dummy comments makes the lines non-empty, so we will not ge
    [all...]
  /src/tests/usr.bin/xlint/lint1/
check-expect.lua 8 Check that the /* expect+-n: ... */ comments in the .c source files match the
61 -- Load the 'expect:' comments from a C source file.
  /src/usr.bin/xlint/lint1/
README.md 7 * It reads the output of the C preprocessor, retaining the comments.
227 Each test can override the lint flags using comments of the following forms:
233 They do this by placing `expect` comments near the location of the diagnostic.
240 There may be other code or comments in the same line of the `.c` file.
check-msgs.lua 8 Check that the message text in the comments of the C source code matches the
  /src/distrib/sets/
regpkg 568 "${rundir}/comments")"

Completed in 28 milliseconds

1 2