diff options
Diffstat (limited to 'README.txt')
| -rw-r--r-- | README.txt | 22 |
1 files changed, 18 insertions, 4 deletions
@@ -1,5 +1,5 @@ ===============
-pycparser v2.02
+pycparser v2.03
===============
:Author: `Eli Bendersky <http://eli.thegreenplace.net>`_
@@ -62,8 +62,8 @@ Installing Prerequisites
-------------
-* ``pycparser`` was tested on Python 2.5, 2.6 and 3.1, on both Linux and Windows
-* ``pycparser`` uses the PLY module for the actual lexer and parser construction. Install PLY version 3.3 (earlier versions work at least since 2.5) from `its website <http://www.dabeaz.com/ply/>`_.
+* ``pycparser`` was tested on Python 2.6 and 3.2, on both Linux and Windows. It should work on any later version (in both the 2.x and 3.x lines) as well.
+* ``pycparser`` uses the PLY module for the actual lexer and parser construction. Install PLY from `its website <http://www.dabeaz.com/ply/>`_.
Installation process
--------------------
@@ -92,7 +92,7 @@ On the vast majority of Linux systems, ``cpp`` is installed and is in the PATH. What about the standard C library headers?
------------------------------------------
-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 in 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 C files.
+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 C files.
See the ``using_cpp_libc.py`` example for more details.
@@ -154,6 +154,20 @@ Some people have contributed to ``pycparser`` by opening issues on bugs they've Changelog
=========
++ Version 2.03 (06.03.2011)
+
+ - Bug fixes:
+
+ * Issue 17: empty file-level declarations
+ * Issue 18: empty statements and declarations in functions
+ * Issue 19: anonymous structs & union fields
+ * Issue 23: fix coordinates of Cast nodes
+
+ - New example added (``examples/c-to-c.py``) for translating ASTs generated by ``pycparser`` back into C code.
+ - ``pycparser`` is now on PyPI (Python Package Index)
+ - Created `FAQ <http://code.google.com/p/pycparser/wiki/FAQ>`_ on the ``pycparser`` project page
+ - Removed support for Python 2.5. ``pycparser`` supports Python 2 from 2.6 and on, and Python 3.
+
+ Version 2.02 (10.12.2010)
* The name of a ``NamedInitializer`` node was turned into a sequence of nodes
|