<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 10:34:36 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Community News: Namespace Operator Debate Ends with Backslash]]></title>
      <guid>http://www.phpdeveloper.org/news/11293</guid>
      <link>http://www.phpdeveloper.org/news/11293</link>
      <description><![CDATA[<p>
For those that have been keeping up with the namespace debate in the PHP community lately (the issue was the operator that would be used), it seems that a <a href="http://wiki.php.net/rfc/namespaceseparator">decision has been made</a> - the backslash (  ) is the character of choice.
</p>
<p>From <a href="http://pooteeweet.org/blog/0/1331">Lukas Smith's blog</a>:</p>
<blockquote>
So today we had an IRC meeting to discuss namespaces in PHP. We came to a <a href="http://wiki.php.net/rfc/namespaceseparator">final decision</a> replacing the current double colon separator with a backslash to solve ambiguity issues with the current syntax. So far there has not been much of a reaction on list, except for a <a href="http://news.php.net/php.internals/41375">post</a> which mentioned concerns related to the fact that backslash is currently used for escaping, but which was quickly <a href="http://news.php.net/php.internals/41376">responded by Greg</a> to point out that yes we were aware of this, but it is not an issue if you know how to use the backslash properly in double quote strings.
</blockquote>
<p>
You can find out more about this implementation using the backslash on <a href="http://wiki.php.net/rfc/backslashnamespaces">this entry</a> in the PHP.net wiki (near the bottom of the page).
</p>]]></description>
      <pubDate>Mon, 27 Oct 2008 11:15:27 -0500</pubDate>
    </item>
  </channel>
</rss>
