<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Use Ruby-style tags in PHP</title>
	<atom:link href="http://robrosenbaum.com/php/use-ruby-style-tags-in-php/feed/" rel="self" type="application/rss+xml" />
	<link>http://robrosenbaum.com/php/use-ruby-style-tags-in-php/</link>
	<description>PHP, JavaScript, and Other Things</description>
	<lastBuildDate>Wed, 25 Feb 2009 11:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rob</title>
		<link>http://robrosenbaum.com/php/use-ruby-style-tags-in-php/comment-page-1/#comment-74</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sun, 21 Oct 2007 16:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://robrosenbaum.com/?p=6#comment-74</guid>
		<description>halfer-
&lt;p&gt;My article concerned ASP-style tags, not PHP short tags; the two are often confused, even on the PHP dev forum. Short tags create a syntactic conflict with XML, and should be avoided for that reason. ASP-style tags have no such problems. I believe the confusion between the two is the reason so few people use ASP-style tags (that and their name.)&lt;/p&gt;
&lt;p&gt;You are correct that they are less portable, but that is itself due to their infrequent use. If they were the standard rather than the exception - and there is no reason they should not be - then every hosting company would enable them by default. It is for that reason that I recommend using them whenever feasible.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>halfer-</p>
<p>My article concerned ASP-style tags, not PHP short tags; the two are often confused, even on the PHP dev forum. Short tags create a syntactic conflict with XML, and should be avoided for that reason. ASP-style tags have no such problems. I believe the confusion between the two is the reason so few people use ASP-style tags (that and their name.)</p>
<p>You are correct that they are less portable, but that is itself due to their infrequent use. If they were the standard rather than the exception &#8211; and there is no reason they should not be &#8211; then every hosting company would enable them by default. It is for that reason that I recommend using them whenever feasible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: halfer</title>
		<link>http://robrosenbaum.com/php/use-ruby-style-tags-in-php/comment-page-1/#comment-72</link>
		<dc:creator>halfer</dc:creator>
		<pubDate>Wed, 17 Oct 2007 09:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://robrosenbaum.com/?p=6#comment-72</guid>
		<description>You can indeed use the short tags in PHP. However they&#039;re not enabled on every server, which is why the symfony team don&#039;t recommend this approach for code that is intended to be portable (eg if you&#039;re writing a plugin, or an application you intend to distribute). This can cause problems for users who don&#039;t have this kind of control over their htaccess file (some shared hosts can disable it).

There&#039;s nothing wrong with short tags though - if the programmer understands their limitations but wants cleaner code, they should use them.</description>
		<content:encoded><![CDATA[<p>You can indeed use the short tags in PHP. However they&#8217;re not enabled on every server, which is why the symfony team don&#8217;t recommend this approach for code that is intended to be portable (eg if you&#8217;re writing a plugin, or an application you intend to distribute). This can cause problems for users who don&#8217;t have this kind of control over their htaccess file (some shared hosts can disable it).</p>
<p>There&#8217;s nothing wrong with short tags though &#8211; if the programmer understands their limitations but wants cleaner code, they should use them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

