X-Git-Url: http://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_get_wstr.3x.html;h=4623161f6a94f536d0392d61e592973d909644d3;hb=4c9f63c460cb7134f142aa65f6866c175ed77605;hp=0e47dcc2e11ce0eb91c132a0f387c85e01c45951;hpb=cb4427a16794d98049b4d790b810d62217501f9f;p=ncurses.git diff --git a/doc/html/man/curs_get_wstr.3x.html b/doc/html/man/curs_get_wstr.3x.html index 0e47dcc2..4623161f 100644 --- a/doc/html/man/curs_get_wstr.3x.html +++ b/doc/html/man/curs_get_wstr.3x.html @@ -1,6 +1,7 @@ - @@ -35,7 +36,7 @@ curs_get_wstr 3x - +

curs_get_wstr 3x

@@ -58,6 +59,7 @@ int getn_wstr(wint_t *wstr, int n); int wget_wstr(WINDOW *win, wint_t *wstr); int wgetn_wstr(WINDOW *win, wint_t *wstr, int n); + int mvget_wstr(int y, int x, wint_t *wstr); int mvgetn_wstr(int y, int x, wint_t *wstr, int n); int mvwget_wstr(WINDOW *win, int y, int x, wint_t *wstr); @@ -133,30 +135,31 @@ X/Open curses documented these functions to pass an array of wchar_t in 1997, but that was an error because of this part of the description: - The effect of get_wstr() is as though a series of calls to - get_wch() were made, until a newline character, end-of-line - character, or end-of-file character is processed. + The effect of get_wstr is as though a series of calls to get_wch + were made, until a newline character, end-of-line character, or + end-of-file character is processed. - The latter function get_wch() can return a negative value, while - wchar_t is a unsigned type. All of the vendors implement this using - wint_t, following the standard. + The latter function get_wch can return a negative value, while wchar_t + is a unsigned type. All of the vendors implement this using wint_t, + following the standard. - X/Open Curses issue 7 is unclear regarding whether the terminating null - wchar_t value is counted in the length parameter n. X/Open Curses is- - sue 7 revised the corresponding description of wgetnstr to address this - issue. The unrevised description of wget_nwstr can be interpreted ei- - ther way. This implementation counts the terminator in the length. + X/Open Curses, Issue 7 (2009) is unclear regarding whether the termi- + nating null wchar_t value is counted in the length parameter n. X/Open + Curses, Issue 7 revised the corresponding description of wgetnstr to + address this issue. The unrevised description of wget_nwstr can be in- + terpreted either way. This implementation counts the terminator in the + length. - X/Open Curses does not specify what happens if the length n is nega- + X/Open Curses does not specify what happens if the length n is nega- tive. - o For analogy with wgetnstr, ncurses 6.2 uses a limit (based on + o For analogy with wgetnstr, ncurses 6.2 uses a limit (based on LINE_MAX). - o Some other implementations (such as Solaris xcurses) do the same, + o Some other implementations (such as Solaris xcurses) do the same, while others (PDCurses) do not allow this. - o NetBSD 7 curses imitates ncurses 6.1 in this regard, treating a -1 + o NetBSD 7 curses imitates ncurses 6.1 in this regard, treating a -1 as an indefinite number of characters.