On Mon, 18 Jul 2011, Matthias Klose wrote:
On 07/18/2011 07:35 AM, Ray Dillinger wrote:
On 07/17/2011 05:10 PM, Thomas Dickey wrote:
You're seeing implicit for get_wch, since there's no _XOPEN_SOURCE_EXTENDED
in the compile line.
Okay, after checking:
bear@janus:~/src/xxh$ make
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 mi
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
On Sun, 15 Jan 2006, Falk Hueffner wrote:
Thomas Dickey <[EMAIL PROTECTED]> writes:
char buf[5];
[...]
The buf variable contains "Key01"
So 6 bytes. Does this still happen if you don't overrun buf? Also,
can you send a complete test case?
It doesn't
On Sun, 15 Jan 2006, Falk Hueffner wrote:
Thomas Dickey <[EMAIL PROTECTED]> writes:
char buf[5];
[...]
The buf variable contains "Key01"
So 6 bytes. Does this still happen if you don't overrun buf? Also,
can you send a complete test case?
ah. I didn't
Package: g++-4.0
Version: 4.0.2-5
Severity: important
Retesting ncurses c++ demo, I get an exception in code which hasn't
changed for several months and which has no apparent error (checked
with valgrind). This function
void TestApplication::init_labels(Soft_Label_Key_Set& S) const
{
for(int
6 matches
Mail list logo
