<?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>Sun, 19 May 2013 20:13:28 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Erik's Blog: PHP implementation of an LALR1 parser generator]]></title>
      <guid>http://www.phpdeveloper.org/news/13869</guid>
      <link>http://www.phpdeveloper.org/news/13869</link>
      <description><![CDATA[<p>
<i>Erik</i> has <a href="http://sankuru.biz/en/blog/7-figuring-out-compiler-technology/121-php-implementation-of-an-lalr1-parser-generator.html">posted about a new parser he's created</a>, one based on the <a href="http://en.wikipedia.org/wiki/LALR_parser">LALR parser method</a>, that can be <a href="http://sankuru.biz/downloads/lrparsers.zip">downloaded here</a> [zip].
</p>
<blockquote>
Parser tables, along with a lexer table, are the core constituents of any compiler's front end. This LALR parser generator is heavily based on my custom Php version of the <a href="http://en.wikipedia.org/wiki/MapReduce">map/reduce programming technique</a> (functional programming). I will elaborate in future posts, on why I used a map/reduce basis to implement the parser generator.
</blockquote>
<p>
Parsers organize a set of tokens based on the rules of a formal language the parser is given. Several of the grammar text files are included in the download so you can test it out for yourself. For more on the topic check out <a href="http://sankuru.biz/en/blog/7-figuring-out-compiler-technology/122-the-need-for-lalr1-packrat-parsers.html">these</a> <a href="http://sankuru.biz/en/blog/7-figuring-out-compiler-technology/123-the-essence-of-map-reduce-programming.html">two</a> posts.
</p>]]></description>
      <pubDate>Tue, 19 Jan 2010 13:03:57 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Ben Ramsey's Blog: Technical Vocabulary and Grammar]]></title>
      <guid>http://www.phpdeveloper.org/news/4713</guid>
      <link>http://www.phpdeveloper.org/news/4713</link>
      <description><![CDATA[With his own <a href="http://benramsey.com/archives/technical-vocabulary-and-grammar/">response</a> to <a href="http://shiflett.org/archive/183">this post</a>, <i>Ben Ramsey</i> sheds some more light on the misspoken technology terms/conventions that pop up over and over.
<p>
<quote>
<i>
This is in response to Chris Shiflett's "<a href="http://shiflett.org/archive/183">Technical Vocabulary and Grammar</a>" post. My comment became so long that I decided to blog it instead.
<p>
Being someone with a degree in English...
</i>
</quote>
<p>
He <a href="http://benramsey.com/archives/technical-vocabulary-and-grammar/">talks about</a> collective nouns being plural (making it okay to use something like "PHPDeveloper.org are..."), periods inside quotation marks, a suggestion for aiding understanding of actual commands typed for programming books (loose the quotes and go bold), and his own view on what "PC" really means...]]></description>
      <pubDate>Mon, 23 Jan 2006 07:43:45 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Technical Vocabulary and Grammar]]></title>
      <guid>http://www.phpdeveloper.org/news/4694</guid>
      <link>http://www.phpdeveloper.org/news/4694</link>
      <description><![CDATA[It's not strictly PHP related, but <i>Chris Shiflett</i> has posted <a href="http://shiflett.org/archive/183">this new item</a> on his blog today with a look at some technical vocabulary and grammar.
<p>
<quote>
<i>
I sometimes wonder why people feel so compelled to use technical terms when talking about computers, even when they don't know what the terms mean. In my experience, those who know the least about a particular topic use the most complicated vocabulary when discussing it. I considered compiling a list of the popular ones, but since I'm lazy and have a blog, I decided to blog about it instead. Feel free to add to the list.
</i>
</quote>
<p>
<a href="http://shiflett.org/archive/183">He mentions</a> the incorrect use of the term "computer" when referring to hardware (overgeneralization), the confusion over very similar technical words (i.e. Orientated and Oriented, Depreciated and Deprecated), the pluralization of company names, and various other issues. Be sure to <a href="http://shiflett.org/archive/183#comments">check out the comments</a> for even more... ]]></description>
      <pubDate>Fri, 20 Jan 2006 06:50:51 -0600</pubDate>
    </item>
  </channel>
</rss>
