Re: [patch] New libstdc++ docs on testing and library versioning

2016-08-18 Thread Jonathan Wakely
On 07/08/16 23:36 -0600, Sandra Loosemore wrote: On 08/04/2016 06:37 PM, Jonathan Wakely wrote: I've been working on some changes to the libstdc++ manual recently. A lot of the changes are just using DocBook markup with more semantic meaning (e.g. or instead of using for everything that

Re: [patch] New libstdc++ docs on testing and library versioning

2016-08-07 Thread Sandra Loosemore
On 08/04/2016 06:37 PM, Jonathan Wakely wrote: I've been working on some changes to the libstdc++ manual recently. A lot of the changes are just using DocBook markup with more semantic meaning (e.g. or instead of using for everything that should use a monospace font) but there are some

Re: [patch] New libstdc++ docs on testing and library versioning

2016-08-05 Thread Jonathan Wakely
On 05/08/16 01:37 +0100, Jonathan Wakely wrote: The core of the new guidelines for writing tests is this: [begin] Test cases that use features of a particular C++ standard should specify the minimum required standard as an effective target: // { dg-do run { target c++11 } } or // {

[patch] New libstdc++ docs on testing and library versioning

2016-08-04 Thread Jonathan Wakely
I've been working on some changes to the libstdc++ manual recently. A lot of the changes are just using DocBook markup with more semantic meaning (e.g. or instead of using for everything that should use a monospace font) but there are some changes to content too. I've added a new subsection