The standard configuration is not such that PHP is set up to process XML or XHTML documents. It is very deliberate that we have a separate mime-type and our own .php extension as the default config. Yes, you can configure PHP to parse all .html files, or .xhtml or even .xml if you wanted to, but that would require a configuration change. As such, one of those changes then might include turning short_tags off.
The golden rules of PHP are to keep the WTF(*) factor low and the POTFP(**) factor high. (*) What The Fuck (**) Piss Off The Fewest People By suddenly changing a basic characteristic of PHP that has been around since the beginning of time in order to solve a problem almost nobody has, we violate both principles, and on top of that we add a security risk in that now people are likely to expose code that they didn't mean to expose and before they figure it out they may have leaked database passwords and other sensitive data. What is needed here is decent documentation, not ramming a configuration change down peoples' throats with absolutely no regard to the consequences and ramifications of such a change. -Rasmus On Sun, 28 Apr 2002, Yasuo Ohgaki wrote: > I really don't understand why we should keep short_tag=on. This > implies we have following _standard_ and _portable_ syntax for > all XML documents preprocessed by PHP. > > <?php echo '<?xml version="1.0" ?>' ?> > > Who vote for this _standard_ and _portable_ syntax? > > Don't forget to write why this syntax is good, > look great, etc. > > -- > Yasuo Ohgaki > > > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
