Home
last modified time | relevance | path

Searched full:comments (Results 1 – 25 of 41) sorted by relevance

12

/nrf52832-nimble/rt-thread/components/net/uip/doc/
H A Duip-code-style.c26 /* Single line comments look like this. */
29 * Multi-line comments look like this. Comments should prefferably be
104 * Static (non-global) functions do not need Doxygen comments. The
/nrf52832-nimble/rt-thread/documentation/
H A Dcoding_style_en.txt39 4. Header File Comments
105 Please use English to comment. There shouldn't be too much comments and the
106 comments should describe what does the code do. And it should describe how the
107 complicated algorithm works. Comments to statements should be placed before them
H A DDoxyfile161 # comments will behave just like regular Qt-style comments
168 # comment as the brief description. If set to NO, the comments
169 # will behave just like regular Qt-style comments (thus requiring
176 # comments) as a brief description. This used to be the default behaviour.
802 # fragments. Normal C and C++ comments will always remain visible.
1605 # You can define message sequence charts within doxygen comments using the \msc
/nrf52832-nimble/packages/NimBLE-latest/
H A DCODING_STANDARDS.md137 ## Comments section in Coding Style for Apache Mynewt Core
139 * No C++ style comments allowed.
156 * All public APIs should be commented with Doxygen style comments describing
/nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/
H A Dzlib.3100 (Request for Comments) 1950 to 1952 in the files:
133 Send questions and/or comments to [email protected],
H A DREADME.eCos18 changes are marked by __ECOS__ (comments or definitions). Finally, the
H A DChangeLog14 - Fix some spelling errors in comments [Betts]
59 - Improve WinCE errno handling and comments [Chang]
65 - Add FAQ entry and comments in deflate.c on uninitialized memory access
76 - Fix inflate header crc check bug for file names and comments
95 - Update zlib.h comments on gzip in-memory processing
312 - Enchance comments in zlib.h on what happens if gzprintf() tries to
H A DREADME5 (Request for Comments) 1950 to 1952 in the files
H A Dinflate.c30 * - Add comments on state->bits assertion in inffast.c
31 * - Add comments on op field in inftrees.h
44 * - Add comments in inffast.c to introduce the inflate_fast() routine
63 * - Added comments in inffast.c on effectiveness of POSTINC
H A Ddeflate.h273 * See deflate.c for comments about the MIN_MATCH+1.
/nrf52832-nimble/rt-thread/components/net/uip/doc/html/
H A Da00051.html41 <a name="l00026"></a>00026 <span class="comment">/* Single line comments look like this. */</span>
44 <a name="l00029"></a>00029 <span class="comment"> * Multi-line comments look like this. Comments sh…
119 …104 <span class="comment"> * Static (non-global) functions do not need Doxygen comments. The</span>
/nrf52832-nimble/packages/NimBLE-latest/docs/
H A DREADME.rst6 The source code also contains inline comments in `Doxygen`_
H A Ddoxygen.xml194 # style comments (thus requiring an explicit @brief command for a brief
202 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
209 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
214 # Note that setting this tag to YES also means that rational rose comments are
304 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
971 # Fortran comments will always remain visible.
2134 # You can define message sequence charts within doxygen comments using the \msc
/nrf52832-nimble/rt-thread/examples/test/
H A Ddhry.h82 * for their help with comments on earlier versions of the
176 * - dhry.h (this file, containing global definitions and comments)
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/netif/ppp/
H A Dvj.h55 * toward small packets (see comments on MTU/MSS below), changes
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/netif/ppp/
H A Dvj.h59 * toward small packets (see comments on MTU/MSS below), changes
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/netif/ppp/
H A Dvj.h52 * toward small packets (see comments on MTU/MSS below), changes
/nrf52832-nimble/packages/NimBLE-latest/nimble/controller/
H A Dsyscfg.yml160 period boundaries. See comments in ble_ll_sched.h for more details.
/nrf52832-nimble/rt-thread/tools/
H A Dkconfiglib.py231 which also holds the title for menus and comments. For Symbol and Choice,
480 comments:
481 A list with all comments, in the same order as they appear in the Kconfig
614 "comments",
750 self.comments = []
1019 # lines or comments. 'line' has already been
1335 # write_config() that doesn't write any comments (including
1336 # '# CONFIG_FOO is not set' comments). The format matches the C
2426 self.comments.append(node)
4584 and comments also get menu nodes. If a symbol or choice is defined in
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/apps/
H A Dhttpd.h154 * style block comments in the form / * # name * / (without the spaces).
/nrf52832-nimble/rt-thread/tools/kconfig-frontends/scripts/.autostuff/scripts/
H A Ddepcomp273 # the IRIX cc adds comments like '#:fec' to the end of the
441 # Much of this is similar to the tru64 case; see comments there.
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/doxygen/
H A Dlwip.Doxyfile186 # style comments (thus requiring an explicit @brief command for a brief
194 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
201 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
206 # Note that setting this tag to YES also means that rational rose comments are
296 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
988 # Fortran comments will always remain visible.
2227 # You can define message sequence charts within doxygen comments using the \msc
H A Dlwip.Doxyfile.cmake.in186 # style comments (thus requiring an explicit @brief command for a brief
194 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
201 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
206 # Note that setting this tag to YES also means that rational rose comments are
296 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
988 # Fortran comments will always remain visible.
2227 # You can define message sequence charts within doxygen comments using the \msc
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/doxygen/
H A Dlwip.Doxyfile186 # style comments (thus requiring an explicit @brief command for a brief
194 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
201 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
206 # Note that setting this tag to YES also means that rational rose comments are
296 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
977 # Fortran comments will always remain visible.
2204 # You can define message sequence charts within doxygen comments using the \msc
/nrf52832-nimble/rt-thread/components/finsh/
H A Dfinsh_token.c212 /* line comments, set to end of file */ in token_run()

12