diff options
| -rw-r--r-- | README.html | 41 | ||||
| -rw-r--r-- | README.txt | 8 | ||||
| -rw-r--r-- | TODO.txt | 2 |
3 files changed, 21 insertions, 30 deletions
diff --git a/README.html b/README.html index ba12dbb..93969da 100644 --- a/README.html +++ b/README.html @@ -323,28 +323,27 @@ ul.auto-toc { <li><a class="reference internal" href="#what-is-it-good-for" id="id4">1.2 What is it good for?</a></li>
<li><a class="reference internal" href="#which-version-of-c-does-pycparser-support" id="id5">1.3 Which version of C does pycparser support?</a></li>
<li><a class="reference internal" href="#what-grammar-does-pycparser-follow" id="id6">1.4 What grammar does pycparser follow?</a></li>
-<li><a class="reference internal" href="#what-is-an-ast" id="id7">1.5 What is an AST?</a></li>
-<li><a class="reference internal" href="#how-is-pycparser-licensed" id="id8">1.6 How is pycparser licensed?</a></li>
-<li><a class="reference internal" href="#contact-details" id="id9">1.7 Contact details</a></li>
+<li><a class="reference internal" href="#how-is-pycparser-licensed" id="id7">1.5 How is pycparser licensed?</a></li>
+<li><a class="reference internal" href="#contact-details" id="id8">1.6 Contact details</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#installing" id="id10">2 Installing</a><ul class="auto-toc">
-<li><a class="reference internal" href="#prerequisites" id="id11">2.1 Prerequisites</a></li>
-<li><a class="reference internal" href="#installation-process" id="id12">2.2 Installation process</a></li>
-<li><a class="reference internal" href="#known-problems" id="id13">2.3 Known problems</a></li>
+<li><a class="reference internal" href="#installing" id="id9">2 Installing</a><ul class="auto-toc">
+<li><a class="reference internal" href="#prerequisites" id="id10">2.1 Prerequisites</a></li>
+<li><a class="reference internal" href="#installation-process" id="id11">2.2 Installation process</a></li>
+<li><a class="reference internal" href="#known-problems" id="id12">2.3 Known problems</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#using" id="id14">3 Using</a><ul class="auto-toc">
-<li><a class="reference internal" href="#interaction-with-the-c-preprocessor" id="id15">3.1 Interaction with the C preprocessor</a></li>
-<li><a class="reference internal" href="#what-about-the-standard-c-library-headers" id="id16">3.2 What about the standard C library headers?</a></li>
-<li><a class="reference internal" href="#basic-usage" id="id17">3.3 Basic usage</a></li>
-<li><a class="reference internal" href="#advanced-usage" id="id18">3.4 Advanced usage</a></li>
+<li><a class="reference internal" href="#using" id="id13">3 Using</a><ul class="auto-toc">
+<li><a class="reference internal" href="#interaction-with-the-c-preprocessor" id="id14">3.1 Interaction with the C preprocessor</a></li>
+<li><a class="reference internal" href="#what-about-the-standard-c-library-headers" id="id15">3.2 What about the standard C library headers?</a></li>
+<li><a class="reference internal" href="#basic-usage" id="id16">3.3 Basic usage</a></li>
+<li><a class="reference internal" href="#advanced-usage" id="id17">3.4 Advanced usage</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#modifying" id="id19">4 Modifying</a></li>
-<li><a class="reference internal" href="#package-contents" id="id20">5 Package contents</a></li>
-<li><a class="reference internal" href="#contributors" id="id21">6 Contributors</a></li>
-<li><a class="reference internal" href="#changelog" id="id22">7 Changelog</a></li>
+<li><a class="reference internal" href="#modifying" id="id18">4 Modifying</a></li>
+<li><a class="reference internal" href="#package-contents" id="id19">5 Package contents</a></li>
+<li><a class="reference internal" href="#contributors" id="id20">6 Contributors</a></li>
+<li><a class="reference internal" href="#changelog" id="id21">7 Changelog</a></li>
</ul>
</div>
<div class="section" id="introduction">
@@ -374,16 +373,12 @@ ul.auto-toc { <h2>1.4 What grammar does pycparser follow?</h2>
<p><tt class="docutils literal"><span class="pre">pycparser</span></tt> very closely follows the C grammar provided in the end of the C99 standard document</p>
</div>
-<div class="section" id="what-is-an-ast">
-<h2>1.5 What is an AST?</h2>
-<p><a class="reference external" href="http://en.wikipedia.org/wiki/Abstract_syntax_tree">AST</a> - Abstract Syntax Tree. It is a tree representation of the syntax of source code - a convenient hierarchical data structure that's built from the code and is readily suitable for exploration and manipulation.</p>
-</div>
<div class="section" id="how-is-pycparser-licensed">
-<h2>1.6 How is pycparser licensed?</h2>
+<h2>1.5 How is pycparser licensed?</h2>
<p><a class="reference external" href="http://www.gnu.org/licenses/lgpl.html">LGPL</a></p>
</div>
<div class="section" id="contact-details">
-<h2>1.7 Contact details</h2>
+<h2>1.6 Contact details</h2>
<p>Drop me an email to <a class="reference external" href="mailto:eliben@gmail.com">eliben@gmail.com</a> for any questions regarding <tt class="docutils literal"><span class="pre">pycparser</span></tt>. For reporting problems with <tt class="docutils literal"><span class="pre">pycparser</span></tt> or submitting feature requests, the best way is to open an issue on the <a class="reference external" href="http://code.google.com/p/pycparser/">pycparser page at Google Code</a>.</p>
</div>
</div>
@@ -428,7 +423,7 @@ ul.auto-toc { <div class="section" id="advanced-usage">
<h2>3.4 Advanced usage</h2>
<p>The public interface of <tt class="docutils literal"><span class="pre">pycparser</span></tt> is well documented with comments in <tt class="docutils literal"><span class="pre">pycparser/c_parser.py</span></tt>. For a detailed overview of the various AST nodes created by the parser, see <tt class="docutils literal"><span class="pre">pycparser/_c_ast.cfg</span></tt>.</p>
-<p>In any case, you can always drop me an <a class="reference external" href="mailto:eliben@gmail.com">email</a> for help.</p>
+<p>There's also a <a class="reference external" href="http://code.google.com/p/pycparser/wiki/FAQ">FAQ available here</a>. In any case, you can always drop me an <a class="reference external" href="mailto:eliben@gmail.com">email</a> for help.</p>
</div>
</div>
<div class="section" id="modifying">
@@ -45,12 +45,6 @@ What grammar does pycparser follow? ``pycparser`` very closely follows the C grammar provided in the end of the C99 standard document
-
-What is an AST?
----------------
-
-`AST <http://en.wikipedia.org/wiki/Abstract_syntax_tree>`_ - Abstract Syntax Tree. It is a tree representation of the syntax of source code - a convenient hierarchical data structure that's built from the code and is readily suitable for exploration and manipulation.
-
How is pycparser licensed?
--------------------------
@@ -112,7 +106,7 @@ Advanced usage The public interface of ``pycparser`` is well documented with comments in ``pycparser/c_parser.py``. For a detailed overview of the various AST nodes created by the parser, see ``pycparser/_c_ast.cfg``.
-In any case, you can always drop me an `email <eliben@gmail.com>`_ for help.
+There's also a `FAQ available here <http://code.google.com/p/pycparser/wiki/FAQ>`_. In any case, you can always drop me an `email <eliben@gmail.com>`_ for help.
Modifying
=========
@@ -7,6 +7,8 @@ Fixes since last: * Issue 17: empty file-level declarations
* Issue 18: empty statements and declarations in functions
+* Created FAQ on the pycparser project page - the readme now points to it
+
Version Update
--------------
|