Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28837
Return-Path: <asbjorn@asbjorn.biz>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 96462 invoked by uid 1010); 14 Apr 2007 20:14:29 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 96447 invoked from network); 14 Apr 2007 20:14:29 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 14 Apr 2007 20:14:29 -0000
Authentication-Results: pb1.pair.com smtp.mail=asbjorn@asbjorn.biz; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=asbjorn@asbjorn.biz; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain asbjorn.biz designates 217.195.185.3 as permitted sender)
X-PHP-List-Original-Sender: asbjorn@asbjorn.biz
X-Host-Fingerprint: 217.195.185.3 mail.asbjorn.biz Linux 2.4/2.6
Received: from [217.195.185.3] ([217.195.185.3:51330] helo=mail.asbjorn.biz)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 9B/61-14447-32631264 for <internals@lists.php.net>; Sat, 14 Apr 2007 16:14:28 -0400
Received: from [82.150.72.200] (82-150-72-200.rev.grenaas.net [82.150.72.200])
	by mail.asbjorn.biz (Postfix) with ESMTP id CC3DC4D0F6
	for <internals@lists.php.net>; Sat, 14 Apr 2007 22:14:23 +0200 (CEST)
Message-ID: <462135A1.2080605@asbjorn.biz>
Date: Sat, 14 Apr 2007 22:12:17 +0200
User-Agent: Icedove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: internals@lists.php.net
References: <461E894C.104@zend.com> <461F7449.7060003@herballure.com>	 <d8269d910704130716s2b9efbbw577c09d3627a24a3@mail.gmail.com>	 <37936.216.230.84.67.1176500697.squirrel@www.l-i-e.com>	 <d8269d910704131454x69e4c25bm4279997ab572c5b8@mail.gmail.com>	 <bcb7aa500704131721y2fed50a3u736df191fd0e6ab3@mail.gmail.com>	 <46209A3F.8040701@mediawave.nl> <4620C93F.6080709@gmail.com>	 <bcb7aa500704140901p4874126fm3b62e378f0f6f096@mail.gmail.com>	 <262916757.20070414180726@marcus-boerger.de>	 <bcb7aa500704140954w7b0d4266s5e39e37976891133@mail.gmail.com>	 <4210606331.20070414191706@marcus-boerger.de>	 <612DC248-6238-4796-AEF4-3208EB0BAAEF@krug.dk> <1176573387.2039.48.camel@blobule>
In-Reply-To: <1176573387.2039.48.camel@blobule>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] dropping asp_tags in HEAD
From: asbjorn@asbjorn.biz (=?ISO-8859-1?Q?Asbj=F8rn_Sloth_T=F8nnesen?=)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Cummings wrote:
> On Sat, 2007-04-14 at 19:51 +0200, Edin Kadribasic wrote:
>> Hello Marcus,
>>
>> I'm afraid you got it backwards. PHP source does not have to comply  
>> with XML, or for that matter any other spec. The result of the PHP  
>> code execution, should the desired output be XML, would of course  
>> have to be.
>>
>> So what the XML specification say is irrelevant for this discussion.  
>> The problem that I was referring to was that PHP will not be able to  
>> parse XML if you have short_tags enabled.
> 
> Actually it's very relevant depending on your intentions. Advanced
> WYSIWYG template engines may wish to treat the raw PHP document as an
> XML document to manipulate the nodes as with any XML document. Without
> an XML compliant markup then this becomes an issue.

So you mean that a new XML compatible syntax should be introduced?

<script type="text/php"><![CDATA[
...
]]></script>

and

<php valueof="$var"/> and <?php=$var?>
instead of or slowly replace
<?=$var?> and <%=$var%>


I like <?php= over <?echo because its the same amount of chars and the
first clearly indicates that it's PHP-related.

I think that short_tags should be removed because of XML compatibility
and asp_tags to avoid PHP code to be confused as ASP, by newbies trying
to learn PHP or ASP. What if ASP Classic in Longhorn server will support
<? or <?php as opening tag, would that just be great?

A gentle way to drop support for short_tags and asp_tags, could be to
drop support for them in php.ini, but still allow the few people using
them to enable it in .htaccess or similar, or force people to recompile
PHP to add support for it. Ok, now I am being mean :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGITWhSViWlxucwuoRAgHQAJ92JWOErdi9150j+lRiNLeGNkkjRgCeLbYb
hslgTPXPR7s1c4IizrVxx90=
=NCw+
-----END PGP SIGNATURE-----