Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you look at the <a href="http://www.aquaphoenix.com/ref/gnu_c_library/libc_239.html" rel="nofollow noreferrer">definition of special characters</a>, that should mean (thre '-1' value), that all those special characters are active:</p> <blockquote> <p>In canonical input, the terminal driver recognizes a number of special characters which perform various control functions.<br> These include the <code>ERASE</code> character (usually <kbd>DEL</kbd>) for editing input, and other editing characters.<br> The INTR character (normally <kbd>Ctrl</kbd>-<kbd>c</kbd>) for sending a <code>SIGINT</code> signal, and other signal-raising characters, may be available in either canonical or noncanonical input mode.</p> </blockquote> <p>And you have a lot of those specal characters:</p> <ul> <li><a href="http://www.aquaphoenix.com/ref/gnu_c_library/libc_240.html#SEC240" rel="nofollow noreferrer">Characters for Input Editing</a></li> <li><a href="http://www.aquaphoenix.com/ref/gnu_c_library/libc_241.html#SEC241" rel="nofollow noreferrer">BSD Extensions to Editing Characters</a></li> <li><a href="http://www.aquaphoenix.com/ref/gnu_c_library/libc_242.html#SEC242" rel="nofollow noreferrer">Characters that Cause Signals</a></li> <li><a href="http://www.aquaphoenix.com/ref/gnu_c_library/libc_243.html#SEC243" rel="nofollow noreferrer">Special Characters for Flow Control</a></li> <li><a href="http://www.aquaphoenix.com/ref/gnu_c_library/libc_244.html#SEC244" rel="nofollow noreferrer">Other Special Characters</a></li> </ul> <hr> <p>The question has been raised to see if <a href="http://www.open-std.org/jtc1/sc22/WG15/docs/rr/9945-1/9945-1-27.html" rel="nofollow noreferrer">such a value was portable</a> (did always compiled) in 1997:</p> <blockquote> <p>The wording in section 2.9.4:</p> <p>If any of the constants in Table 2-11 are defined to have value -1 in the header ....</p> <p>can suggest, on casual reading, code like the following to minimize size and optimize efficiency for each implementation:</p> </blockquote> <pre><code>#ifdef _POSIX_VDISABLE #if _POSIX_VDISABLE == -1 /* code that assumes no vdisable capability */ #else /* code that assumes vdisable capability */ #endif #else /* code that uses pathconf() to determine vdisable capability */ #endif </code></pre> <p>The <a href="http://standards.ieee.org/reading/ieee/interp/1003-1-90_int/pasc-1003.1-34.html" rel="nofollow noreferrer">interpretation #34</a> suggests that it will.</p> <blockquote> <p>By using these values at COMPILE-TIME, a portable POSIX.1 application can avoid loading all pathconf() related code associated with a symbol in Table 2-11 when the symbol is defined.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload