Searched refs:follows (Results 1 – 25 of 42) sorted by relevance
12
| /glibc-2.36/manual/ |
| D | README.tunables | 28 format of the file is as follows:
81 module using the TUNABLE_GET macro as follows:
89 The callback function should be defined as follows:
106 form of the macros as follows:
124 from that module, use the full form of the macros as follows:
|
| D | dynlink.texi | 116 the program header, so it follows its convention, and the address is not
|
| D | locale.texi | 205 @code{setlocale}. Call it as follows:
595 as far as the system follows the Unix standards.
843 as follows:
1435 return value is as follows:
|
| D | ctype.texi | 669 @code{if} cascades, but rewriting the code as follows is wrong:
683 problem is to write the code as follows:
|
| D | maint.texi | 147 follows:
282 The 64-bit-time implementation of @code{localtime} is written as follows
|
| D | argp.texi | 375 where the arguments are as follows:
620 special @samp{--} argument. This prevents anything that follows from
901 follows:
|
| D | charset.texi | 479 clearing the whole variable with code such as follows:
1649 This set of functions follows the traditional cycle of using a resource:
2133 follows is a step-by-step analysis of the points raised above. The
2221 aliases follows below.
2461 @code{__invocation_counter} as follows:
2733 chance. Whether another step follows can be determined from the
|
| D | message.texi | 333 is as follows:
486 GNU implementation follows this specification and so processes
624 call the @code{gencat} program as follows (assume @file{ex.msg} contains
1742 message catalog. It is composed as follows:
|
| D | intro.texi | 47 generally follows the same division as the header files.
533 follows: objects whose types are exposed to users, and that users are
605 The identifier that follows the @code{const} mark will appear by itself
|
| D | math.texi | 634 proper way to test the result of @code{ilogb} is as follows:
1102 function or you can compute the values as follows:
1305 accuracy of functions without fully specified results are as follows;
|
| D | nss.texi | 17 @w{Solaris 2}. @Theglibc{} follows their name and calls this
|
| D | arith.texi | 2643 This function attempts to decompose @var{string} as follows:
2968 This function attempts to decompose @var{string} as follows:
2994 The hexadecimal format is as follows:
3131 precision follows, which starts with a period, @samp{.}, and may be
|
| D | memory.texi | 958 You could define @code{calloc} as follows:
2332 declared as follows:
2375 in the current chunk. It is declared as follows:
3075 using @dfn{memory protection keys}. These restrictions work as follows:
|
| D | stdio.texi | 829 to the stream. This is not what follows from the @w{ISO C} locale model
3816 If a caret character @samp{^} immediately follows the initial @samp{[},
3915 If the @samp{%n} follows the locus of a matching failure, then no value
5223 programmer follows some minimal requirements.
5466 Unix program @code{cat}. The explanation of the error follows and the
|
| D | startup.texi | 81 pointer always follows the last element: @code{@var{argv}[@var{argc}]}
|
| D | sysinfo.texi | 601 name one also knows the filesystem name. Nevertheless here follows the
|
| /glibc-2.36/benchtests/ |
| D | README | 13 benchmark by invoking make as follows:
31 benchmark to use clock_gettime by invoking make as follows:
40 as follows:
78 To run only a subset of benchmarks, one may invoke make as follows
|
| /glibc-2.36/posix/ |
| D | regexec.c | 3273 re_node_set follows; in build_trtable() local
3303 err = re_node_set_alloc (&follows, ndests + 1); in build_trtable()
3307 re_node_set_free (&follows); in build_trtable()
3319 re_node_set_empty (&follows); in build_trtable()
3326 err = re_node_set_merge (&follows, dfa->eclosures + next_node); in build_trtable()
3331 dest_states[i] = re_acquire_state_context (&err, dfa, &follows, 0); in build_trtable()
3338 dest_states_word[i] = re_acquire_state_context (&err, dfa, &follows, in build_trtable()
3347 dest_states_nl[i] = re_acquire_state_context (&err, dfa, &follows, in build_trtable()
3437 re_node_set_free (&follows); in build_trtable()
|
| D | BOOST.tests | 353 ; now follows various complex expressions designed to try and bust the matcher:
|
| /glibc-2.36/localedata/locales/ |
| D | mt_MT | 56 % # This collation follows Maltese Standard DMS MSA 200:2009
|
| /glibc-2.36/timezone/ |
| D | africa | 485 # Cabinet Decision of July 18th, 2008 states as follows:
724 # Scattered Islands (Iles Eparses) administered from Reunion are as follows.
|
| D | asia | 722 # But Rives McDow (2000-06-18) quotes a contact in Iraqi-Kurdistan as follows:
1028 # Shanks & Pottenger write that DST in Japan during those years was as follows:
1418 # the rest of the country follows the Ulaanbaatar time, which is UTC/GMT plus
|
| D | southamerica | 661 # effective today (00:00am at June 24, 2008) as follows:
669 # This change follows a proposal of senator Tiao Viana of Acre state, that
|
| D | europe | 207 # and follows the more usual convention of putting the location name first,
1329 # publication. When the three sources disagree, guess who's right, as follows:
1966 # still follows Moscow time, no matter where in Russia it is located.
|
| D | northamerica | 1026 # but the only part of Labrador that follows the rules is the
1857 # at 2:00 AM, the times in each zone are as follows:
1862 # 3. The rest of the year, the times are as follows:
|
12