Try to catch up _GLIBCXX_RESOLVE_LIB_DEFECTS comments and documentation.

2014-03-15 Thread Ed Smith-Rowland
I'm resending this because I forgot to dupe to gcc-patches and I'd like one thread. This should be pure commentary and documentation. I hope I got all these. I grepped for DR and added _GLIBCXX_RESOLVE_LIB_DEFECTS where it seemed needed. I did not add in cases where DR mentions were more com

Re: Try to catch up _GLIBCXX_RESOLVE_LIB_DEFECTS comments and documentation.

2014-03-16 Thread Jonathan Wakely
On 15 March 2014 14:46, Ed Smith-Rowland wrote: > I'm resending this because I forgot to dupe to gcc-patches and I'd like one > thread. > > This should be pure commentary and documentation. > > I hope I got all these. I grepped for DR and added > _GLIBCXX_RESOLVE_LIB_DEFECTS where it seemed needed

Re: Try to catch up _GLIBCXX_RESOLVE_LIB_DEFECTS comments and documentation.

2014-03-16 Thread Ed Smith-Rowland
On 03/16/2014 08:43 AM, Jonathan Wakely wrote: On 15 March 2014 14:46, Ed Smith-Rowland wrote: I'm resending this because I forgot to dupe to gcc-patches and I'd like one thread. This should be pure commentary and documentation. I hope I got all these. I grepped for DR and added _GLIBCXX_RESO

Re: Try to catch up _GLIBCXX_RESOLVE_LIB_DEFECTS comments and documentation.

2014-03-17 Thread Jonathan Wakely
On 16 March 2014 16:09, Ed Smith-Rowland wrote: > OK, thinking further on it I actually agree with not mentioning DRs on a > partially baked standard. We advertise that support for new standards is > experimental. I don't think it does any harm to add comments during the C++1y/C++1z process to no