rfc:flexible_heredoc_nowdoc_syntaxes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:flexible_heredoc_nowdoc_syntaxes [2017/11/15 20:04]
tpunt
rfc:flexible_heredoc_nowdoc_syntaxes [2018/04/13 19:59] (current)
nikic Implementation landed
Line 3: Line 3:
   * Date: 2017-09-16   * Date: 2017-09-16
   * Author: Thomas Punt, tpunt@php.net   * Author: Thomas Punt, tpunt@php.net
-  * Status: Accepted+  * Status: Implemented (in PHP 7.3)
   * First Published at: https://wiki.php.net/rfc/flexible_heredoc_nowdoc_syntaxes   * First Published at: https://wiki.php.net/rfc/flexible_heredoc_nowdoc_syntaxes
  
Line 136: Line 136:
 </code> </code>
  
-This change was actually brought up in a previous RFC ([[rfc:heredoc-scanner-loosening|PHP RFC: Loosening heredoc/nowdoc scanner]]). One of the big gotchas that it mentioned, however, was that if the ending marker was found at the start of a line, then regardless of whether it was apart of another word, it would still be considered as the ending marker. For example, the following would not work (due to ''ENDING'' containing ''END''):+This change was actually brought up in a previous RFC ([[rfc:heredoc-scanner-loosening|PHP RFC: Loosening heredoc/nowdoc scanner]]). One of the big gotchas that it mentioned, however, was that if the ending marker was found at the start of a line, then regardless of whether it was a part of another word, it would still be considered as the ending marker. For example, the following would not work (due to ''ENDING'' containing ''END''):
 <code php> <code php>
 $values = [<<<END $values = [<<<END
rfc/flexible_heredoc_nowdoc_syntaxes.1510776294.txt.gz · Last modified: 2017/11/15 20:04 by tpunt