-----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----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
