This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: 4.4 use static_assert or #warning for unimplemented c++0x std libs
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Chris <indy271828 at sympatico dot ca>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 5 Jan 2009 12:56:40 -0800
- Subject: Re: 4.4 use static_assert or #warning for unimplemented c++0x std libs
- References: <BLU0-SMTP39B2472EA972F5079454DFADE10@phx.gbl>
On Mon, Jan 05, 2009 at 11:39:55AM -0800, Chris wrote:
> Is it possible to have some sort of protocol in gcc, so that any
> unimplemented library function uses #warning or static_assert(0,"regex
> not implemented") to not to confuse any future users? I don't think
> gcc should provide headers that compile but don't do anything.
Yes, it will make it awful hard for autoconf users trying to determine
if a feature is supported, if use of that feature produces functions that
compile, link, and do nothing with a report of success.