summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorEli Bendersky <eliben@gmail.com>2015-05-10 08:10:12 -0700
committerEli Bendersky <eliben@gmail.com>2015-05-10 08:10:12 -0700
commite9f5bc7c8a00e71df1255f8df15979336034fdaa (patch)
tree5eb1189fe686001fa98a238e7e73ce4c7a3cb0cc /README.rst
parentc830da88193cff670180b57eee95712fe1f01b07 (diff)
downloadpycparser-e9f5bc7c8a00e71df1255f8df15979336034fdaa.tar.gz
Mention cffi use in the README
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/README.rst b/README.rst
index 095f3a1..0cafea7 100644
--- a/README.rst
+++ b/README.rst
@@ -33,6 +33,9 @@ Anything that needs C code to be parsed. The following are some uses for
* Automatic unit-test discovery
* Adding specialized extensions to the C language
+One of the most popular uses of **pycparser** is in the `cffi
+<https://cffi.readthedocs.org/en/latest/>`_ library, which uses it to parse the
+declarations of C functions and types in order to auto-generate FFIs.
**pycparser** is unique in the sense that it's written in pure Python - a very
high level language that's easy to experiment with and tweak. To people familiar
with Lex and Yacc, **pycparser**'s code will be simple to understand.