Re: PHP Dev RFC Selecting Namespaces and Tag styles at include time.
| From: | Bradley Proctor | Date: | Thu, 09 Dec 2010 21:26:19 +0000 |
| Subject: | Re: PHP Dev RFC Selecting Namespaces and Tag styles at include time. | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50980@lists.php.net to get a copy of this message | ||
On Thu, Dec 9, 2010 at 3:53 PM, Michael Morris <dmgx.michael@gmail.com>wrote:
>
> PHP_TAGS_NONE is suggested as a possible bonus mode this approach allows
> that wouldn't be feasible otherwise. In this mode the engine treats the
> whole file as PHP and doesn't allow mode switching. This might allow the
> engine to parse the file faster. Importantly it would allow framework
> designers to enforce that certain files not have HTML in them - such as a
> database class, or a custom child class. Admittedly it doesn't stop
> echo'ing the html, but it drives home the point to all but the densest that
> perhaps this isn't the place to be printing/echoing. It's use would
> encounter the problem of current IDE tools assuming that a PHP file will
> always have a starting <?php tag.
>
>
This also would help prevent accidentally putting whitespace before the
<?php that
can cause problems with header()