Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36567
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.170.191 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=RqJstOWOszWi3NVIso7bBedaVxMXWMlOqLQAxcyrihh5hquhlbw9jBnwI7CHU99ersRCCnkwNWXtacOrrUpVNST9lkfwKZC8vIBXJGrG6l0rpBu8Wrc475xfidEUlOYqRFcJQzzwXyTOfZ/pJ/a1swWv6xhkNrCgOWjqpVhp/Kk=
Message-ID: <7f3ed2c30803261321n7cc60bf2l48c4c5418af2cf73@mail.gmail.com>
Date: Wed, 26 Mar 2008 21:21:08 +0100
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "Derick Rethans" <derick@php.net>, "Marcus Boerger" <helly@php.net>, 
	"PHP Internals" <internals@lists.php.net>
In-Reply-To: <47EAAA45.4000103@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47E3F714.60302@zend.com>
	 <883216194.20080321193140@marcus-boerger.de>
	 <47E40848.1060103@zend.com>
	 <7f3ed2c30803211412v299a0c36m86cabb27b26c232@mail.gmail.com>
	 <47E42657.7010408@zend.com>
	 <1222637984.20080321222647@marcus-boerger.de>
	 <47E42AB6.7010401@zend.com>
	 <alpine.DEB.0.98.0803261130520.31437@kossu.ez.no>
	 <47EAAA45.4000103@zend.com>
Subject: Re: [PHP-DEV] short_open_tag
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

On Wed, Mar 26, 2008 at 8:55 PM, Stanislav Malyshev <stas@zend.com> wrote:
> Hi!
>
>
>  > I don't think I've ever said I don't like short tags. It's not the issue
>  > here. The issue is that allowing to change it during runtime adds more
>  > WTF to PHP. WTF factors are bad.
>
>  OK, there were people saying short tags are mortal sin, devil's device
>  to lure pure souls into the hell and what not. Good that you don't :)
>  Speaking of the WTF, I don't really see any major WTF since:
>  1. 99.9% of the code (except for parser XML templates) works with any
>  tags settings. One that wouldn't work will bail out immediately with
>  clearly recognized error message, so the problem would be easy to locate
>  and fix.
>  2. For any code messing with this value - and this code should be only
>  one place in whole application, the template engine - it is very easy to
>  restore it afterwards, and any programmer smart enough to write in PHP
>  would know to do that.
>  3. There are a bunch of runtime settings that some code can influence
>  other code with - most prominent being include path - and we had very
>  little problem with them being INI_ALL.
>  4. This change actually does not remove any existing scenarios and adds
>  one previously impossible - having short tag templates in the context
>  where enabling short tags for whole application is not desired.


You do know that having short tags enabled will result in a parse
error in the following situation, right?:
foo.php
<?xml version="1.0">
<root>
<?php
foreach($array as $el => $val) {
    printf('<%s>%s</%2$s>', $el, $val);
}
?>
</root>

I actually think that by now the most common way to do exactly this
is: echo '<?xml version="1.0">'; so being PHP_INI_ALL isn't the worst
idea ever - but I still think it'll just create more wtf then
necessary.

-Hannes