Re: where should C++ options be documented?

2018-04-04 Thread Eric Gallager
On 4/2/18, Martin Sebor wrote: > Jason, > > The manual mentions some C++-only options in the language > independent section 3.8 Options to Request or Suppress > Warnings and others in 3.5 Options Controlling C++ Dialect. > > For example, -Wcatch-value, -Wconditionally-supported,

Re: where should C++ options be documented?

2018-04-04 Thread Jason Merrill
On Wed, Apr 4, 2018 at 2:18 PM, Martin Sebor wrote: > On 04/04/2018 07:05 AM, Jason Merrill wrote: >> >> On Tue, Apr 3, 2018 at 7:05 PM, Martin Sebor wrote: >>> >>> On 04/03/2018 08:08 AM, Jason Merrill wrote: On Mon, Apr 2, 2018 at 9:33 PM, Martin

Re: where should C++ options be documented?

2018-04-04 Thread Martin Sebor
On 04/04/2018 07:05 AM, Jason Merrill wrote: On Tue, Apr 3, 2018 at 7:05 PM, Martin Sebor wrote: On 04/03/2018 08:08 AM, Jason Merrill wrote: On Mon, Apr 2, 2018 at 9:33 PM, Martin Sebor wrote: Jason, The manual mentions some C++-only options in the

Re: where should C++ options be documented?

2018-04-04 Thread Martin Sebor
Let me try gzipping the attachment to see if it gets past SpamAssassin. On 04/04/2018 11:08 AM, Martin Sebor wrote: On 04/04/2018 05:49 AM, Nathan Sidwell wrote: On 04/03/2018 07:05 PM, Martin Sebor wrote: @@ -3914,6 +3916,7 @@ Options} and @ref{Objective-C and Objective-C++ Di -Wc++11-compat

Re: where should C++ options be documented?

2018-04-04 Thread Jason Merrill
On Tue, Apr 3, 2018 at 7:05 PM, Martin Sebor wrote: > On 04/03/2018 08:08 AM, Jason Merrill wrote: >> On Mon, Apr 2, 2018 at 9:33 PM, Martin Sebor wrote: >>> >>> Jason, >>> >>> The manual mentions some C++-only options in the language >>> independent section

Re: where should C++ options be documented?

2018-04-04 Thread Nathan Sidwell
On 04/03/2018 07:05 PM, Martin Sebor wrote: @@ -3914,6 +3916,7 @@ Options} and @ref{Objective-C and Objective-C++ Di -Wc++11-compat -Wc++14-compat @gol -Wcatch-value @r{(C++ and Objective-C++ only)} @gol -Wchar-subscripts @gol +-Wclass-memaccess @r{(C++ and Objective-C++ only)} @gol

Re: where should C++ options be documented?

2018-04-03 Thread Martin Sebor
On 04/03/2018 06:20 AM, David Brown wrote: On 03/04/18 03:33, Martin Sebor wrote: Jason, The manual mentions some C++-only options in the language independent section 3.8 Options to Request or Suppress Warnings and others in 3.5 Options Controlling C++ Dialect. For example, -Wcatch-value,

Re: where should C++ options be documented?

2018-04-03 Thread Martin Sebor
On 04/03/2018 08:08 AM, Jason Merrill wrote: On Mon, Apr 2, 2018 at 9:33 PM, Martin Sebor wrote: Jason, The manual mentions some C++-only options in the language independent section 3.8 Options to Request or Suppress Warnings and others in 3.5 Options Controlling C++

Re: where should C++ options be documented?

2018-04-03 Thread Jason Merrill
On Mon, Apr 2, 2018 at 9:33 PM, Martin Sebor wrote: > Jason, > > The manual mentions some C++-only options in the language > independent section 3.8 Options to Request or Suppress > Warnings and others in 3.5 Options Controlling C++ Dialect. > > For example, -Wcatch-value,

Re: where should C++ options be documented?

2018-04-03 Thread David Brown
On 03/04/18 03:33, Martin Sebor wrote: > Jason, > > The manual mentions some C++-only options in the language > independent section 3.8 Options to Request or Suppress > Warnings and others in 3.5 Options Controlling C++ Dialect. > > For example, -Wcatch-value, -Wconditionally-supported, > and

where should C++ options be documented?

2018-04-02 Thread Martin Sebor
Jason, The manual mentions some C++-only options in the language independent section 3.8 Options to Request or Suppress Warnings and others in 3.5 Options Controlling C++ Dialect. For example, -Wcatch-value, -Wconditionally-supported, and -Wzero-as-null-pointer-constant are mentioned only on