<?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>Sat, 25 May 2013 01:28:34 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Community News: Namespaces in PHP6]]></title>
      <guid>http://www.phpdeveloper.org/news/8194</guid>
      <link>http://www.phpdeveloper.org/news/8194</link>
      <description><![CDATA[<p>
Spurred on by a <a href="http://schlitt.info/applications/blog/exit.php?url_id=3868&entry_id=556">recent post</a> to the php-dev mailing list by <i>Dmitry Stogov</i> the ever-popular "namespaces discussion" has surged back to the top of everyone's list. <i>Dmitry</i> proposed <a href="http://dev.daylessday.org/diff/tests.tar.gz">a patch</a> for PHP6 that would easily implement namespaces for the upcoming version.
</p>
<blockquote>
All class and function names inside are automatically prefixed with namespace name. Inside namespace, local name always takes precedence over global name. It is possible to use the same namespace in several PHP files. The namespace declaration statement must be the very first statement in
file.
</blockquote>
<p>
The general idea is to provide an easy separation of functionality but to keep things accessible at any level (in scope, in parent scope, etc). He's <a href="http://marc.info/?l=php-dev&m=118355320225178&w=2">included code</a> in his mailing list post to illustrate how it would all work.
</p>
<p>
Several others in the PHP community have jumped on and are already talking about this new proposal:
</p>
<ul>
<li><a href="http://www.rooftopsolutions.nl/article/139">Evert Pot's post</a>
<li>a <a href="http://www.phpguru.org/#127">blog entry</a> from <i>Richard Heyes</i> proposing a namespace character
<li><a href="http://php100.wordpress.com/2007/07/05/namespaces-can-we-keep-it-simple/">a new post</a> from the PHP 10.0 Blog on simplicity in namespaces
<li><a href="http://www.tonybibbs.com/article.php/NamespacesInPHP6">this new post</a> from <i>Tony Bibbs</i>
<li><a href="http://schlitt.info/applications/blog/index.php?/archives/556-I-love-namespaces.html">some thoughts from</a> <i>Tobias Schlitt</i> happily supporting the proposal
<li><a href="http://www.dynamicwebpages.de/99.rdfnews.php?select=1170">this post</a> from DynamicWebPages.de
</ul>]]></description>
      <pubDate>Fri, 06 Jul 2007 11:10:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Matthew Weir O'Phinney's Blog: exuberant ctags with PHP in Vim]]></title>
      <guid>http://www.phpdeveloper.org/news/7202</guid>
      <link>http://www.phpdeveloper.org/news/7202</link>
      <description><![CDATA[<p>
In a <a href="http://weierophinney.net/matthew/archives/134-exuberant-ctags-with-PHP-in-Vim.html">new post</a>, <i>Matthew Weir O'Phinney</i> sharing a handy new tool that he discovered - <a href="http://weierophinney.net/matthew/archives/ctags.sourceforge.net">exuberant ctags</a> - that lets you magically click on a class of function name and move to its declaration.
</p>
<blockquote>
I found <a href="http://weierophinney.net/matthew/archives/ctags.sourceforge.net">exuberant ctags</a>, a library which can be used to generate an index file mapping language objects to source files and the line in the source file where they are declared. Contrary to its name, it's not just for the C language; it currently supports 33 different programming languages, including PHP.
</blockquote>
<p>
He also includes a usage example in <a href="http://weierophinney.net/matthew/archives/134-exuberant-ctags-with-PHP-in-Vim.html">the post</a>, specifically for getting the tool up and working in your Vim installation (via a bash script). Then it's just a matter of issuing a :set command to point at the correct file and you're one keystroke away from the function/class declaration of your choice.
</p>]]></description>
      <pubDate>Thu, 01 Feb 2007 07:17:46 -0600</pubDate>
    </item>
  </channel>
</rss>
