Re: Quick question about closing PHP tags

From: Date: Mon, 02 Feb 2009 08:55:26 +0000
Subject: Re: Quick question about closing PHP tags
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-42883@lists.php.net to get a copy of this message
On Mon, Feb 2, 2009 at 10:28 AM, mike <mike503@gmail.com> wrote: > There's some discussion going on -discuss about whether or not to > close PHP tags. > > The Zend Framework says to not use them... > > > http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html#coding-standard.php-file-formatting.general > > Is there any opinion from the internals/PHP experts on this? Is there > any technical or performance reason to include them or go without > them? > > Obviously the bonus is no stupid human error/whitespace type issues > with output buffering and such. But I wanted to know if there's any > opinion either way for any other reasons? > > Thanks. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > While on this subject, would it be a waste of time to suggest a file extension or include/require parameter that would consider a whole file as php even if there is no starting <?php tag? Would save a lot of people from bothering with leading whitespaces, BOM, etc. It could go as far as to completely ignore php tags in the whole document and imply that contains 100% php code. There are quite some libraries/frameworks/etc that would benefit from this and maybe if the parser didn't have to check for tags could result in a very small performance boost? G.

« previous php.internals (#42883) next »