Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43681
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.179 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=o4WrEADyIsAQtQK7IviB2J89xJjbSHQbTYleZc8RTPyXVjhhHrXRkAOJaIfxhtTIOi
         trHWkyi4fJiLPl0na6OFuCmJRSBX/kW6UjaIOOBniPB7w+ZHa/8CSvTjXDJryGIw7O4k
         8Cjm5O9l+zbdZqn/eE9aTXPEXXnYpoX0buWZo=
Message-ID: <49E38E10.3080102@gmail.com>
Date: Mon, 13 Apr 2009 21:10:08 +0200
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Jeremy <jeremy@pinacol.com>
CC: internals@lists.php.net
References: <49E352FD.6070008@gmail.com> <DB.C3.22673.B3373E94@pb1.pair.com>
In-Reply-To: <DB.C3.22673.B3373E94@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Is it true that short_open_tag is deprecated in
 PHP 6?
From: glen.84@gmail.com (Glen)

It was not my intention to initiate a massive debate regarding the use
of short_open_tag.

I posted for two reasons:

1. To ask if short_open_tag has been deprecated in PHP 6.
2. To suggest asp_tags as the recommended option for templating in PHP
(to keep both crowds* happy).

* The crowd *for* the use of short_open_tag (I don't believe that they
are in favour of this tag because of the particular characters used, but
rather because of its shortness), and the crowd *against* its use
(believing that, since PHP's primary use is for embedding code within
HTML documents, it should respect the use of other processing instructions).

Glen.

Jeremy wrote:
> Glen wrote:
>>
>> It's short, and it doesn't conflict with XML.
>>
>
> I have to say, I don't understand all the hate on short_open_tag.  So
> what if it "conflicts" with XML?  PHP is not XML.  If you use an XML
> construct in your PHP, escape it.  PHP can generate a lot of other
> languages, too -- should every construct from these languages be
> forbidden in PHP as well?
>
> Jeremy
>