This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.0 & backward compatibility for libstdc++
- To: Ingo Krabbe <i dot krabbe at dokom dot net>
- Subject: Re: gcc 3.0 & backward compatibility for libstdc++
- From: Laurent Pinchart <laurent dot pinchart at capflow dot com>
- Date: Sat, 23 Jun 2001 16:12:01 +0200
- CC: gcc-help at gcc dot gnu dot org
- References: <Pine.LNX.4.33.0106231602580.20855-100000@flathead.burg.de>
- Reply-To: laurent dot pinchart at capflow dot com
> I cannot believe, though I don't know it, that ncurses really insists on
> vscan.
From cursew.cc :
int
NCursesWindow::scanw(int y, int x, const char* fmt, ...)
{
#if defined(__GNUG__)
va_list args;
va_start(args, fmt);
char buf[BUFSIZ];
int result = wmove(w, y, x);
if (result == OK) {
result = wgetstr(w, buf);
if (result == OK) {
strstreambuf ss(buf, sizeof(buf));
result = ss.vscan(fmt, (_IO_va_list)args);
}
}
va_end(args);
return result;
#else
return ERR;
#endif
}
And no internal implementation of strstreambuf::vscan. And there's no
way in the configure process to prevent __GNUG__ from being defined.
Should I do it 'by hand' ? I'll lose some functionality then, and will
probably break the library.
Any help about how to install a libstdc++-v2 is still welcome :-)
Laurent Pinchart