On Sun, 17 Jul 2011, Ray Dillinger wrote:
On 07/17/2011 05:10 PM, Thomas Dickey wrote:
fwiw, I routinely build with warnings enabled (and don't have a use for
-Werror).
For the rest - I'm typically seeing only extra warnings that
you wouldn't see with -Wall (such as const mismatches, which are
problematic).
That's for ncurses itself, plus lynx and dialog.
curses.h isn't including <wctype.h>, since none of its declarations need it.
That's iswgraph and iswspace.
You're seeing implicit for get_wch, since there's no _XOPEN_SOURCE_EXTENDED
in the compile line. Quoting from man ncurses
Wait, the compile line? I took the documentation you quote for ncurses
below....
The standard implies that, and some implementations (I've been burned by
gcc with cygwin as well as more than one vendor Unix) put their predefined
stuff _outside_ any #includes). Best practice puts that on the compile
line.
I'll check and see if I can use --Wall or --Werror with the ncursesw
library if I include _X_OPEN_SOURCE_EXTENDED on the gcc command line
instead of (or in addition to) in the file. But it still can't be
correct behavior for these compile options to have an effect on what
functions are visible/linkable.
yes - but in the report all I saw was the implied declaration aspect,
which is enough for -Werror to whine and die. That's not really the
same as linkable.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
