Commits

Eli Bendersky committed a4d3f2b

update license, changes file and README

Comments (0)

Files changed (5)

++ Version 2.09 (??)
+
+  - pycparser now carries its PLY dependency along. The pycparser/ply directory
+    contains the source of PLY for the currently supported version. This makes
+    distribution and testing easier.
+
 + Version 2.08 (10.08.2012)
 
   - Issue 73: initial support for #pragma directives. Consume them without
-Copyright (c) 2011, Eli Bendersky
+Copyright (c) 2012, Eli Bendersky
 All rights reserved.
 
 Redistribution and use in source and binary forms, with or without modification,
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 <meta name="generator" content="Docutils 0.8.1: http://docutils.sourceforge.net/" />
-<title>pycparser v2.08</title>
+<title>pycparser v2.09</title>
 <meta name="author" content="Eli Bendersky" />
 <style type="text/css">
 
 </style>
 </head>
 <body>
-<div class="document" id="pycparser-v2-08">
-<h1 class="title">pycparser v2.08</h1>
+<div class="document" id="pycparser-v2-09">
+<h1 class="title">pycparser v2.09</h1>
 <table class="docinfo" frame="void" rules="none">
 <col class="docinfo-name" />
 <col class="docinfo-content" />
 <div class="section" id="what-about-the-standard-c-library-headers">
 <h2>3.2&nbsp;&nbsp;&nbsp;What about the standard C library headers?</h2>
 <p>C code almost always includes various header files from the standard C library, like <tt class="docutils literal">stdio.h</tt>. While, with some effort, <tt class="docutils literal">pycparser</tt> can be made to parse the standard headers from any C compiler, it's much simpler to use the provided &quot;fake&quot; standard  includes in <tt class="docutils literal">utils/fake_libc_include</tt>. These are standard C header files that contain only the bare necessities to allow valid parsing of the files that use them. As a bonus, since they're minimal, it can significantly improve the performance of parsing large C files.</p>
+<p>The key point to understand here is that <tt class="docutils literal">pycparser</tt> doesn't really care aabout the semantics of types. It only needs to know whether some token encountered in the source is a previously defined type. This is essential in order to be able to parse C correctly.</p>
 <p>See the <tt class="docutils literal">using_cpp_libc.py</tt> example for more details.</p>
 </div>
 <div class="section" id="basic-usage">
 ===============
-pycparser v2.08
+pycparser v2.09
 ===============
 
 :Author: `Eli Bendersky <http://eli.thegreenplace.net>`_
 
 C code almost always includes various header files from the standard C library, like ``stdio.h``. While, with some effort, ``pycparser`` can be made to parse the standard headers from any C compiler, it's much simpler to use the provided "fake" standard  includes in ``utils/fake_libc_include``. These are standard C header files that contain only the bare necessities to allow valid parsing of the files that use them. As a bonus, since they're minimal, it can significantly improve the performance of parsing large C files.
 
+The key point to understand here is that ``pycparser`` doesn't really care aabout the semantics of types. It only needs to know whether some token encountered in the source is a previously defined type. This is essential in order to be able to parse C correctly.
+
 See the ``using_cpp_libc.py`` example for more details.
 
 Basic usage
 Todo
 ----
 
-- Write a FAQ about using fake headers
 - Carry PLY around instead of requiring to install it
 - close issue 31 and open new one