/third_party/ffmpeg/doc/ |
D | errno.txt | 7 E2BIG POSIX ++++++ Argument list too long 8 EACCES POSIX ++++++ Permission denied 9 EADDRINUSE POSIX +++..+ Address in use 10 EADDRNOTAVAIL POSIX +++..+ Cannot assign requested address 12 EAFNOSUPPORT POSIX +++..+ Address family not supported 13 EAGAIN POSIX + ++++++ Resource temporarily unavailable 14 EALREADY POSIX +++..+ Operation already in progress 19 EBADF POSIX ++++++ Bad file descriptor 22 EBADMSG POSIX ++4... Bad message 28 EBUSY POSIX - ++++++ Device or resource busy [all …]
|
/third_party/pcre2/pcre2/testdata/ |
D | testoutput18 | 1 # This set of tests is run only with the 8-bit library. It tests the POSIX 3 # not be run with JIT (which is not available for the POSIX interface). 11 ** Ignored with POSIX interface: auto_callout 15 ** Ignored with POSIX interface: find_limits 20 ** Ignored with POSIX interface: partial_hard 24 ** Ignored with POSIX interface: parens_nest_limit 27 ** Ignored with POSIX interface: allow_surrogate_escapes max_pattern_length 57 No match: POSIX code 17: match failed 68 No match: POSIX code 17: match failed 77 Failed: POSIX code 15: bad back reference at offset 6 [all …]
|
D | testoutput19 | 1 # This set of tests is run only with the 8-bit library. It tests the POSIX 4 # POSIX interface). 15 No match: POSIX code 17: match failed
|
/third_party/tzdata/ |
D | time2posix.3.txt | 16 IEEE Standard 1003.1 (POSIX) requires the time_t value 536457599 to 17 stand for 1986-12-31 23:59:59 UTC. This effectively implies that POSIX 24 means that these values will differ from those required by POSIX by the 30 difftime(3). However, POSIX gives an arithmetic expression for 38 POSIX equivalents. This is done by accounting for the number of time- 39 base changes that would have taken place on a POSIX system as leap 42 communicating with POSIX-compliant systems. 45 corresponds to a single POSIX time_t. The posix2time function is less 47 and for a negative leap second hit the corresponding POSIX time_t 49 indicators of the inferiority of the POSIX representation. [all …]
|
D | etcetera | 8 # support for POSIX-style TZ strings. On such platforms these entries 12 # Starting with POSIX 1003.1-2001, the entries below are all 14 # instead of TZ='Etc/GMT+4' one can use the POSIX setting TZ='<-04>+4'. 16 # Do not use a POSIX TZ setting like TZ='GMT+4', which is four hours 36 # Be consistent with POSIX TZ settings in the Zone names, 38 # POSIX has positive signs west of Greenwich, but many people expect 44 # Earlier incarnations of this package were not POSIX-compliant,
|
D | tzfile.5.txt | 63 consistency checking with the POSIX-style TZ string described below.) 85 POSIX-required range [-24:59:59, 25:59:59]. 108 appropriate for another time zone specified via a POSIX-style TZ string 113 with a different UT offset. POSIX does not specify this obsolete 118 on TZ="EET-2EEST,M3.5.0/3,M10.5.0/4" if POSIX conformance is required 130 data comes a newline-enclosed, POSIX-TZ-environment-variable-style 133 The POSIX-style TZ string is empty (i.e., nothing between the newlines) 134 if there is no POSIX representation for such instants. If nonempty, 135 the POSIX-style TZ string must agree with the local time type after the 145 For version-3-format timezone files, the POSIX-TZ-style string may use [all …]
|
/third_party/ltp/testcases/open_posix_testsuite/Documentation/ |
D | HOWTO_Assertions | 30 ref - For reference document (generally a POSIX specification) 38 XBD# - POSIX Base Definitions document 39 XSH# - POSIX System Interfaces document 40 XCU# - POSIX Shell and Utilities document 41 XRAT# - POSIX Rationale document 58 the official POSIX Specs, then simply put in 62 pt:<POSIXtag> - If the assertion is taken from a POSIX specification and there 63 is a POSIX tag (pt) associated with it, the additional string 65 POSIX tag.
|
D | COVERAGE.signals | 5 This document lists the items that will be tested for POSIX signals. 16 the POSIX Test Suite creators are listed below. 20 Tag - tag that applies to the function in the POSIX spec 21 Complexity - POSIX test suite owners' intuitions at complexity of the function 23 Recommended? - set to "NO" if the POSIX spec recomments using *other* 25 Priority - POSIX test suite owners' intuitions at priorities of these 67 - Any additional information listed in the POSIX System Interfaces document 69 - Any functional requirements listed in the POSIX Base Definitions document. 70 (ex. Testing that each signal listed in the POSIX Base Definitions
|
D | HOWTO_FunctionalStressTest | 10 Functional tests test the behavior of functional areas of the POSIX* 11 specification. They do not relate directly to lines in the POSIX 19 taxed by excessively using the functional areas in the POSIX specification 20 or monitoring how the functional areas in the POSIX specification behave 30 Each of these are further subdivided into POSIX area (Timers, Semaphores, 33 Within the functional/<POSIX area> directory, you should create the 71 - create directories corresponding to POSIX chapters (see .1-1990 or 75 * POSIX (R) is a registered trademark of the IEEE
|
D | HOWTO_BugReporting | 2 POSIX Test Test Suites. 5 POSIX Test Test Suites. 15 - Code under test that is targeted* for the POSIX Test Suite reporting. 29 4. If the code under test is compatible with another POSIX version (e.g., 45 *targeted implementation = an implementation which POSIX Test Suite will 47 **Process for tracing a test case to previous POSIX specifications not
|
D | HOWTO_ConformanceTest | 10 Conformance tests test conformance to the POSIX* specification. They test 23 definitions/ - This directory contains tests for each *.h file in the POSIX 27 POSIX spec. Tests are taken from the System Interfaces document. 62 Tests which the POSIX spec uses the words "may" or "implementation-defined" 90 * POSIX (R) is a registered trademark of the IEEE
|
/third_party/boost/libs/regex/doc/ |
D | syntax_option_type.qbk | 43 // Options common to both Perl and POSIX regular expressions: 55 // POSIX extended specific options: 59 // POSIX basic specific options: 163 [section:syntax_option_type_extended Options for POSIX Extended Regular Expressions] 166 [link boost_regex.syntax.basic_extended POSIX extended 172 expression engine is the same as that used by POSIX extended regular 174 (POSIX ), Base Definitions and Headers, Section 9, Regular Expressions (FWD.1). 176 Refer to the [link boost_regex.syntax.basic_extended POSIX extended 180 (The POSIX standard specifies that only "special" characters may be 183 engine is the same as that used by POSIX utility grep when given the [all …]
|
D | faq.qbk | 24 [*Q.] Why does using parenthesis in a POSIX regular expression change the 27 [*A.] For POSIX (extended and basic) regular expressions, but not for perl regexes, 29 When the expression is compiled as a POSIX basic or extended regex then Boost.Regex 30 follows the POSIX standard leftmost longest rule for determining what matched. 52 [*Q.] Why don't character ranges work properly (POSIX mode only)? 54 [*A.] The POSIX standard specifies that character range expressions are 57 most locales other than "C" or "POSIX", [A-Z] would match the single 65 this also applies to the POSIX API functions which use either
|
D | syntax_basic.qbk | 9 [section:basic_syntax POSIX Basic Regular Expression Syntax] 13 The POSIX-Basic regular expression syntax is used by the Unix utility `sed`, 14 and variations are used by `grep` and `emacs`. You can construct POSIX 18 // e1 is a case sensitive POSIX-Basic expression: 20 // e2 a case insensitive POSIX-Basic expression: 23 [#boost_regex.posix_basic][h3 POSIX Basic Syntax] 25 In POSIX-Basic regular expressions, all characters are match themselves except 134 By default, for POSIX-Basic regular expressions, a character /x/ is within the 217 [link boost_regex.posix_basic POSIX-Basic expressions], 222 will match either of the [link boost_regex.posix_basic POSIX-Basic expressions] [all …]
|
D | syntax_extended.qbk | 9 [section:basic_extended POSIX Extended Regular Expression Syntax] 13 The POSIX-Extended regular expression syntax is supported by the POSIX 15 `egrep` and `awk`. You can construct POSIX extended regular expressions in 18 // e1 is a case sensitive POSIX-Extended expression: 20 // e2 a case insensitive POSIX-Extended expression: 23 [#boost_regex.posix_extended_syntax][h3 POSIX Extended Syntax] 25 In POSIX-Extended regular expressions, all characters match themselves except for 141 [caution The POSIX standard does not support back-references for "extended" 167 By default, for POSIX-Extended regular expressions, a character /x/ is 230 The POSIX standard defines no escape sequences for POSIX-Extended [all …]
|
/third_party/ltp/testcases/open_posix_testsuite/ |
D | BUILD | 1 Build Notes for POSIX Test Suite 5 The POSIX Test Suite should be able to be run independently of any given 6 OS, so the OS-specific steps for configuring the POSIX Test Suite to run 36 POSIX message queues have been available in FreeBSD since 6.x. Please add: 56 POSIX semaphores have been available in FreeBSD since 5.x. Please add: 64 Notes for running POSIX Test Suite against Linux implementations of 65 POSIX functionality. (Note: If these implementations are accepted into 81 If LinuxThreads is the default POSIX thread implementation, 86 If NPTL is the default POSIX thread implementation, add '-lpthread' to LDLIBS. 108 POSIX Message Queue (Wronski/Benedyczak's implementation) has been [all …]
|
D | README | 3 1. Open POSIX* Test Suite Overview 13 1. Open POSIX* Test Suite Overview 16 The POSIX Test Suite is an open source test suite with the goal of 23 POSIX operating system. 35 - Enable assertion based traceability for conformance testing of POSIX 37 statements about our coverage of the POSIX specification. 74 HOWTO_DefinitionsTest - ideas behind testing POSIX header files 120 The Open POSIX Test Suite is not affiliated with the IEEE or The Open Group. 122 * POSIX (R) is a registered trademark of the IEEE
|
D | NEWS | 13 …S is helping kernel, library and application developers and OSDs on their POSIX related work. Plea… 19 …4-29 cvs pull (NPTL enabled) and linux-2.6.5-mm6 kernel.It is noted that "POSIX Message Queues" ha… 22 POSIX Test Suite 1.4.0 includes more pthread conformance test cases. Now we have test cases coverin… 25 POSIX Test Suite test pass results available for [CVS pull 3-04-04, Kernel 2.6.1, libc-2004-02-15 a… 28 POSIX Test Suite test pass results available for [CVS pull 2-20-04, Kernel 2.6.1, libc-2004-02-01 a…
|
D | QUICK-START | 7 No worries! Here's a quick doc to help you around POSIX** Test Suite. 45 POSIX* Test Suite project page: http://posixtest.sf.net 57 HOWTO_DefinitionsTest - ideas behind testing POSIX header files 62 ** POSIX (R) is a registered trademark of the IEEE
|
/third_party/icu/docs/userguide/ |
D | posix.md | 3 title: C/POSIX Migration 12 # C/POSIX Migration 23 ## Migration from Standard C and POSIX APIs 25 The ISO C and POSIX standards define a number of APIs for string handling and 27 initially designed before Unicode/ISO 10646 were developed, and the POSIX APIs 30 This chapter discusses C/POSIX APIs with their problems, and shows which ICU 33 > :point_right: **Note**: *We use the term "POSIX" to mean the POSIX.1 standard (IEEE Std 1003.1) … 36 standards include POSIX.1 as a subset, adding other specifications that are 39 > :construction: This chapter is not complete yet – more POSIX APIs are expected to be discussed 73 3. The C/POSIX standards only provide a very limited set of useful functions [all …]
|
/third_party/pcre2/pcre2/cmake/ |
D | pcre2-config.cmake.in | 24 # PCRE2::POSIX - The POSIX PCRE2 library. 57 …}${PCRE2_SUFFIX} ${PCRE2_PREFIX}${PCRE2_8BIT_NAME}d${PCRE2_SUFFIX} DOC "8 bit POSIX PCRE2 library") 91 # When POSIX component has been specified make sure that also 8BIT component is specified. 97 elseif (component STREQUAL "POSIX") 103 …message(FATAL_ERROR "The component POSIX is specified while the 8BIT one is not. This is not allow… 131 if (component STREQUAL "POSIX")
|
/third_party/node/doc/api/ |
D | path.md | 16 ## Windows vs. POSIX 23 So using `path.basename()` might yield different results on POSIX and Windows: 25 On POSIX: 42 On POSIX and Windows: 49 To achieve consistent results when working with POSIX file paths on any 52 On POSIX and Windows: 116 * `:` for POSIX 118 For example, on POSIX: 223 For example, on POSIX: 277 For example, on POSIX: [all …]
|
/third_party/libexif/m4m/ |
D | gp-check-shell-environment.m4 | 19 AC_MSG_CHECKING([for POSIX sh \$() command substitution]) 29 * POSIX sh \$() command substition does not work with this shell. 38 * Run this configure script using a better (i.e. POSIX compliant) shell.
|
/third_party/boost/libs/outcome/doc/src/content/reference/functions/ |
D | try_throw_std_exception_from_error.md | 28 The choice to refer to POSIX `errno` values above reflects the matching algorithm. 29 As {{% api "std::errc" %}} exactly maps POSIX `errno`, on all platforms 31 Only on POSIX platforms only are {{% api "std::system_category" %}} error codes
|
/third_party/pcre2/pcre2/src/ |
D | pcre2posix.c | 182 POSIX functions were given pcre2_... names instead of the traditional POSIX 185 uses the POSIX library and the other uses the PCRE2 POSIX functions, thus 186 causing two instances of the POSIX runctions to exist, leading to trouble. For
|