<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://pugs.postgresql.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>parsing</title>
 <link>http://pugs.postgresql.org/taxonomy/term/101</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>SFPUG June: Parsers &amp; pgCon</title>
 <link>http://pugs.postgresql.org/node/405</link>
 <description>Date: Wednesday, June 11th
Time: 7:30 PM
Food: TBA
&lt;a href=&quot;http://casadonde.org&quot;&gt;Directons to Casa Donde&lt;/a&gt;


pgCon Report

Josh Berkus and David Fetter will give a recap of what happened at pgCon for those who missed it, as well as discuss the fallout from that conference, including replication in the core, commitfests, and more. Plus slides!

An Introduction to Parsing

No matter what language you use to write software --
from Basic and C to Java, Python, Perl and SQL -- a
parser is part of the behind-the-scenes machinery. The
parser is an essential part of translating what you
write into something that can be executed. It analyzes
your code and breaks it down into contants, variables,
statements, expressions, punctuation, etc.

We&#039;ll talk about what parsing is, how a parser works,
how parsing integrates with semantic analysis, and
discuss some different types of parsers and
compiler-compilers. We&#039;ll finish with a very brief
look at the PostgreSQL parser.</description>
 <comments>http://pugs.postgresql.org/node/405#comments</comments>
 <category domain="http://pugs.postgresql.org/taxonomy/term/31">SFPUG</category>
 <category domain="http://pugs.postgresql.org/taxonomy/term/39">meeting</category>
 <category domain="http://pugs.postgresql.org/taxonomy/term/101">parsing</category>
 <category domain="http://pugs.postgresql.org/taxonomy/term/102">pgcon</category>
 <pubDate>Wed, 04 Jun 2008 00:25:53 +0100</pubDate>
 <dc:creator>sfpug</dc:creator>
 <guid isPermaLink="false">405 at http://pugs.postgresql.org</guid>
</item>
</channel>
</rss>
