In gcc/doc/: 2011-06-09 Nicola Pero <nicola.pero@meta-innovation.com>

In gcc/doc/:
2011-06-09  Nicola Pero  <nicola.pero@meta-innovation.com>

	* doc/objc.texi (Traditional GNU Objective-C runtime API):
	Updated.

From-SVN: r174823

gcc/ChangeLog

+2011-06-09  Nicola Pero  <nicola.pero@meta-innovation.com>
+
+	* doc/objc.texi (Traditional GNU Objective-C runtime API):
+	Updated.
+
 2011-06-08  Alexandre Oliva  <aoliva@redhat.com>
 
 	* tree-flow-inline.h (op_iter_init): Reject GIMPLE_PHI stmts.

gcc/doc/objc.texi

@@ -121,24 +121,8 @@ different naming convention, such as @code{class_get_super_class()}
 API).  Software using this API includes the file
 @file{objc/objc-api.h} where it is declared.
 
-The traditional API is deprecated but it is still supported in this
-release of the runtime; you can access it as usual by including
-@file{objc/objc-api.h}.
-
-If you are using the traditional API you are urged to upgrade your
-software to use the modern API because the traditional API requires
-access to private runtime internals to do anything serious with it;
-for this reason, there is no guarantee that future releases of the GNU
-Objective-C runtime library will be able to provide a fully compatible
-@file{objc/objc-api.h} as the private runtime internals change.  It is
-expected that the next release will hide a number of runtime internals
-making the traditional API nominally supported but fairly useless
-beyond very simple use cases.
-
-Finally, you can not include both @file{objc/objc-api.h} and
-@file{objc/runtime.h} at the same time.  The traditional and modern
-APIs unfortunately have some conflicting declarations (such as the one
-for @code{Method}) and can not be used at the same time.
+Starting with GCC 4.7.0, the traditional GNU runtime API is no longer
+available.
 
 @c =========================================================================
 @node Executing code before main