Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43688
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.218.167 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:cc:content-type;
        b=L+kEgfWDCi5AvtMjiofVkM+LTXrqxgTgu6VOh8LTlzAcJ22lhU5hDPSq2mCcmzuRjo
         IfF07yg/Fmft/kHVx01UkwB0ZDNA43pyJaMmmLRbZz3siEk5rMjc45I9goxXnxpKO6BN
         3R9PQtuRHqYO84S1gGrU1osDE+7ZSUgzFWe8c=
MIME-Version: 1.0
Sender: kkooporation@googlemail.com
In-Reply-To: <ECCFDCE9-C262-49AC-A0E7-B24A2199A117@roshambo.org>
References: <49E352FD.6070008@gmail.com> <DB.C3.22673.B3373E94@pb1.pair.com> 
	<2dedb8a0904131124u57f2f32ei27083a289f7f18a4@mail.gmail.com> 
	<49E39B3C.2020401@zend.com> <ECCFDCE9-C262-49AC-A0E7-B24A2199A117@roshambo.org>
Date: Tue, 14 Apr 2009 00:48:29 +0200
Message-ID: <bf119e410904131548yf1e4b86l451ea24bec662faa@mail.gmail.com>
To: Philip Olson <philip@roshambo.org>
Cc: Stanislav Malyshev <stas@zend.com>, Kalle Sommer Nielsen <kalle@php.net>, Jeremy <jeremy@pinacol.com>, 
	internals@lists.php.net
Content-Type: multipart/alternative; boundary=001636c5a4af3bed8c046777841d
Subject: Re: [PHP-DEV] Re: Is it true that short_open_tag is deprecated in PHP 
	6?
From: kureal@kkooporation.de (Kenan Sulayman)

--001636c5a4af3bed8c046777841d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hey Guys,

Whenever I start an XHTML document, I do escape it this way:

<<?="?"?>xml version="1.0" encoding="utf-8"?>

Where the <? part will be the output by PHP.

<?="?"?> equals <? print "?" ?> equals <?php print "?" ?>

So, please do not deprecate it - because it's important for me :$

Thanks,
(c) Kenan Sulayman
Freelance Designer and Programmer

Life's Live Poetry



2009/4/14 Philip Olson <philip@roshambo.org>

>
> Today this topic may be the cloudiest and most heated in all of PHP. Here's
> the factual history of our poor little short_open_tag directive:
>
> ------------------------------------------------
> php.ini values : short_open_tag
> ------------------------------------------------
>
> PHP 4, 5_0
>  * Default behaviour   : on
>  * php.ini-dist        : on
>  * php.ini-recommended : on
>
> PHP 5_1, 5_2:
>  * Default behaviour   : on
>  * php.ini-dist        : on
>  * php.ini-recommended : off
>
> PHP 5_3:
>  * Default behaviour   : on
>  * php.ini-development : off
>  * php.ini-production  : off
>
> ------------------------------------------------
> php.ini descriptions : short_open_tag
> ------------------------------------------------
>
> In 5_2 our reason for discouraging it is:
>
> ; - short_open_tag = Off           [Portability]
> ;     Using short tags is discouraged when developing code meant for
> redistribution
> ;     since short tags may not be supported on the target server.
> ; Allow the <? tag. Otherwise, only <?php and <script> tags are recognized.
> ; NOTE: Using short tags should be avoided when developing applications or
> ; libraries that are meant for redistribution, or deployment on PHP
> ; servers which are not under your control, because short tags may not
> ; be supported on the target server. For portable, redistributable code,
> ; be sure not to use short tags.
>
> In 5_3 it's:
>
> ; This directive determines whether or not PHP will recognize code between
> ; <? and ?> tags as PHP source which should be processed as such. It's been
> ; recommended for several years that you not use the short tag "short cut"
> and
> ; instead to use the full <?php and ?> tag combination. With the wide
> spread use
> ; of XML and use of these tags by other languages, the server can become
> easily
> ; confused and end up parsing the wrong code in the wrong context. But
> because
> ; this short cut has been a feature for such a long time, it's currently
> still
> ; supported for backwards compatibility, but we recommend you don't use
> them.
>
> ------------------------------------------------
>
> This history strongly suggests PHP is hoping and subtly forcing the world
> to stop using this directive, and although it's not deprecated the wording
> and treatment makes it feel it could be any day now. This situation must be
> clarified before 5_3 is released, and will likely require our BDFL to do it.
>
> In related news, what came of this RFC? It still says "Under Discussion":
>
>  - http://wiki.php.net/rfc/shortags
>
> Regards,
> Philip
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001636c5a4af3bed8c046777841d--