public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* Remove long-dead deprecation documentation
@ 2018-03-21 11:16 Nathan Sidwell
  2018-03-21 17:10 ` Sandra Loosemore
  0 siblings, 1 reply; 2+ messages in thread
From: Nathan Sidwell @ 2018-03-21 11:16 UTC (permalink / raw)
  To: Sandra Loosemore; +Cc: GCC Patches

[-- Attachment #1: Type: text/plain, Size: 225 bytes --]

Sandra,
this removes the now-deleted deprecated features. AFAICT these have been 
gone for a long time -- 2008 is the most recent changelog entry -- so no 
need to put it in any release notes.

ok?

nathan
-- 
Nathan Sidwell

[-- Attachment #2: feat.diff --]
[-- Type: text/x-patch, Size: 2083 bytes --]

2018-03-21  Nathan Sidwell  <nathan@acm.org>

	* doc/extend.texi (Deprecated Features): Remove mention of
	long-deleted deprecations.

Index: doc/extend.texi
===================================================================
--- doc/extend.texi	(revision 258712)
+++ doc/extend.texi	(working copy)
@@ -23827,19 +23827,9 @@ While the list below is not exhaustive,
 that are now deprecated or have been removed:
 
 @table @code
-@item -fexternal-templates
-@itemx -falt-external-templates
-These are two options provided alternative methods of template
-instantiation.  @xref{Template Instantiation}.  The options have been removed.
-
-@item -fstrict-prototype
-@itemx -fno-strict-prototype
-Previously it was possible to use an empty prototype parameter list to
-indicate an unspecified number of parameters (like C), rather than no
-parameters, as C++ demands.  This feature has been removed.
 
 @item -fno-for-scope
-@item -ffriend-injection
+@itemx -ffriend-injection
 These two options provide compatibility with pre-standard C++.
 @xref{Backwards Compatibility}.
 
@@ -23850,23 +23840,6 @@ by one returning a different pointer typ
 covariant return type rules is now deprecated and will be removed from a
 future version.
 
-The G++ minimum and maximum operators (@samp{<?} and @samp{>?}) and
-their compound forms (@samp{<?=}) and @samp{>?=}) have been deprecated
-and are now removed from G++.  Code using these operators should be
-modified to use @code{std::min} and @code{std::max} instead.
-
-The named return value extension has been deprecated, and is now
-removed from G++.
-
-The use of initializer lists with new expressions has been deprecated,
-and is now removed from G++.
-
-Floating and complex non-type template parameters have been deprecated,
-and are now removed from G++.
-
-The implicit typename extension has been deprecated and is now
-removed from G++.
-
 The use of default arguments in function pointers, function typedefs
 and other places where they are not permitted by the standard is
 deprecated and will be removed from a future version of G++.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Remove long-dead deprecation documentation
  2018-03-21 11:16 Remove long-dead deprecation documentation Nathan Sidwell
@ 2018-03-21 17:10 ` Sandra Loosemore
  0 siblings, 0 replies; 2+ messages in thread
From: Sandra Loosemore @ 2018-03-21 17:10 UTC (permalink / raw)
  To: Nathan Sidwell; +Cc: GCC Patches

On 03/21/2018 05:11 AM, Nathan Sidwell wrote:
> Sandra,
> this removes the now-deleted deprecated features. AFAICT these have been 
> gone for a long time -- 2008 is the most recent changelog entry -- so no 
> need to put it in any release notes.
> 
> ok?

Yes, this is fine.  At some point we might want to do more cleanup here, 
but getting rid of obsolete stuff means there's less left to clean up.  :-)

-Sandra

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-03-21 17:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-21 11:16 Remove long-dead deprecation documentation Nathan Sidwell
2018-03-21 17:10 ` Sandra Loosemore

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).