title: PHP 7 reserved words: resource, object, mixed and numeric
body: <p><a href="https://wiki.php.net/rfc/reserve_even_more_types_in_php_7" rel="nofollow">PHP RFC: Reserve Even More Types in PHP 7</a> claims the following words are now reserved in the context of class, interface and trait names and namespaces: <a href="https://wiki.php.net/rfc/reserve_even_more_types_in_php_7#result" rel="nofollow">resource, object, mixed and numeric</a>.</p>
  
  <p>However, the following code is <a href="https://3v4l.org/JC7NU" rel="nofollow">valid</a> in PHP 7.</p>
  
  <pre><code>class resource {}
  class object {}
  class mixed {}
  class numeric {}
  </code></pre>
  
  <p>I want to call my interface <code>Resource</code> but I would be loathe if PHP suddenly made it a reserved word mid-PHP 7 release stream.</p>
  
  <ul>
  <li>In light of this apparent conflict of an accepted PR with the empirical evidence submitted herein and the <a href="https://github.com/php/php-src/blob/f4d1af7981a4173b25e9ef84fcc550b8b0df72c0/Zend/zend_compile.c#L151-L165" rel="nofollow">absence of any such reservations in the source</a>, should I be safe to call my interface <code>Resource</code>, or not? </li>
  <li>Can a patch for this PR still be implemented in PHP 7.x or must it now wait until PHP-next?</li>
  <li>Is the absence of any commitment to implement it an indicator that it may never be implemented in any future version?</li>
  </ul>
  
  <hr>
  
  <p>EDIT: In light of the discussion that followed highlighting these words have only been <a href="http://php.net/manual/en/reserved.other-reserved-words.php" rel="nofollow"><em>soft reserved</em></a> it seems there is one additional key question to be asked. It seems to me a word should either be reserved or not and that a <em>soft reservation</em> state makes no sense, therefore:</p>
  
  <ul>
  <li>Why was the soft reservation state created instead of "hard" reserving these words?</li>
  </ul>