- Any of these functions other than wgetn_wstr may be macros.
-
- Using get_wstr, mvget_wstr, mvwget_wstr, or wget_wstr to read a line
- that overflows the array pointed to by wstr causes undefined results.
- The use of getn_wstr, mvgetn_wstr, mvwgetn_wstr, or wgetn_wstr,
- respectively, is recommended.
-
- These functions cannot return KEY_ values because there is no way to
- distinguish a KEY_ value from a valid wchar_t value. may be macros.
-
-
All of these functions return the integer OK upon successful
completion. If unsuccessful, they return ERR.
@@ -142,6 +130,18 @@
the window pointer is null.
+
+ Any of these functions other than wgetn_wstr may be macros.
+
+ Using get_wstr, mvget_wstr, mvwget_wstr, or wget_wstr to read a line
+ that overflows the array pointed to by wstr causes undefined results.
+ The use of getn_wstr, mvgetn_wstr, mvwgetn_wstr, or wgetn_wstr,
+ respectively, is recommended.
+
+ These functions cannot return KEY_ values because there is no way to
+ distinguish a KEY_ value from a valid wchar_t value.
+
+
These functions are described in The Single Unix Specification, Version
2. No error conditions are defined.
@@ -172,30 +172,33 @@
X/Open Curses does not specify what happens if the length n is
negative.
- 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,
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.