This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/49894] [C++0x] Uniform initialization in constructor
- From: "jason at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 14 Oct 2011 19:28:42 +0000
- Subject: [Bug libstdc++/49894] [C++0x] Uniform initialization in constructor
- Auto-submitted: auto-generated
- References: <bug-49894-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49894
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |jason at gcc dot gnu.org
Component|c++ |libstdc++
--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> 2011-10-14 19:28:42 UTC ---
The request to support ({ ... }) for array mem-initializers was rejected by
core:
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_closed.html#1339
Now that the compiler supports non-static data member initializers, the library
should use that instead of a mem-initializer.
::pthread_cond_t cond = PTHREAD_COND_INITIALIZER;
should work in all cases.