Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43693
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.221.134 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=rE4FQpgOWEIuasAZ9gb4a+0YXE5KvDHc+vSnw98eoEgaNfnx2srqee4frfUD5J6iMY
         NaNIufG5W+PAOuqKYSFJfGWnLF3VYmuMGPFPS7GiSl3N1kMVbFGP2hIlU40pniWI+lF1
         3vJiDor/0ZJg+hrawzgG28R1077Hc90m1gP0Q=
Message-ID: <49E477CA.9040709@gmail.com>
Date: Tue, 14 Apr 2009 13:47:22 +0200
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Evert | Filemobile <evert@filemobile.com>
CC: Stanislav Malyshev <stas@zend.com>, 
 Kalle Sommer Nielsen <kalle@php.net>,
 Jeremy <jeremy@pinacol.com>, internals@lists.php.net
References: <49E352FD.6070008@gmail.com> <DB.C3.22673.B3373E94@pb1.pair.com> <2dedb8a0904131124u57f2f32ei27083a289f7f18a4@mail.gmail.com> <49E39B3C.2020401@zend.com> <4E5BC7CA-8513-49F5-AEAF-5ABEC2A83EDA@filemobile.com>
In-Reply-To: <4E5BC7CA-8513-49F5-AEAF-5ABEC2A83EDA@filemobile.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)

Right, but at the moment something like:

<?$this->that;?>

... works. i.e. no whitespace after the opening tag.

Changing this would most likely break a fair amount of code.

Glen.

Evert | Filemobile wrote:
>
> On 13-Apr-09, at 4:06 PM, Stanislav Malyshev wrote:
>
>> Hi!
>>
>>> Thats because with short_open_tags on, you need to use:
>>> <?php echo('<?xml ... ?>'); ?>
>>
>> It's a pretty small use case (that's a problem only if you have xml
>> documents which has to have php code which has to be inlined) and as
>> you see, can be easily handled. I think that should not make whole
>> very useful syntax deprecated.
>
> I think the parser should look ahead and check for something like :
>
> /<?(php|[\w])
>
> (either <?php or <? + linebreaks/whitespace).
>
> Evert