- Removed bogus sentence stating that $array[index] is going do be deprecated

'someday'. It simply isn't. Until it isn't decided, this sentence doesn't
  belong in here. Just consider that 'index' could be a defined() constant.
  Also removed comments which made no sense.


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@81475 c90b9560-bf6c-de11-be94-00142212c4b1

language/types.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.77 $ -->
+<!-- $Revision: 1.78 $ -->
  <chapter id="language.types">
   <title>Types</title>
 
@@ -1278,23 +1278,13 @@ $error_descriptions[8] = "This is just an informal notice";
        constant or keyword, and then you get in trouble. For example,
        you already cannot use the words <literal>empty</literal> and 
        <literal>default</literal> this way, since they are special keywords.
-       <!-- <jeroen>hmm... i'm doubting this myself. Finish it if you like</jeroen>
-       But probably 
-       the most threatening
-       thing is yourself, or whoever will maintain the script. You'll 
-       maybe get very strange behaviour, and 
-       -->
-      </para>
-      <para>
-       And, if these arguments don't help: this syntax is simply deprecated,
-       and it might stop working some day.
       </para>
       <note>
        <simpara>
         When you turn <link linkend="function.error-reporting"
         >error_reporting</link> to <literal>E_ALL</literal>,
-        you will see that PHP generates warnings whenever this construct
-        is used. This is also valid for other deprecated 'features'.
+        you will see that PHP generates warnings whenever an
+        <literal>index</literal> is used which is not defined
         (put the line <literal>error_reporting(E_ALL);</literal> 
         in your script)
        </simpara>