| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| c_files/ | 04-Jul-2025 | - | 580 | 304 | ||
| README.rst | D | 04-Jul-2025 | 393 | 9 | 7 | |
| c-to-c.py | D | 04-Jul-2025 | 1.5 KiB | 63 | 30 | |
| c_json.py | D | 04-Jul-2025 | 6.2 KiB | 204 | 107 | |
| cdecl.py | D | 04-Jul-2025 | 6.3 KiB | 200 | 124 | |
| dump_ast.py | D | 04-Jul-2025 | 922 | 28 | 13 | |
| explore_ast.py | D | 04-Jul-2025 | 5.4 KiB | 160 | 29 | |
| func_calls.py | D | 04-Jul-2025 | 1.3 KiB | 48 | 24 | |
| func_defs.py | D | 04-Jul-2025 | 1.3 KiB | 47 | 18 | |
| rewrite_ast.py | D | 04-Jul-2025 | 612 | 32 | 18 | |
| serialize_ast.py | D | 04-Jul-2025 | 907 | 37 | 16 | |
| using_cpp_libc.py | D | 04-Jul-2025 | 871 | 31 | 12 | |
| using_gcc_E_libc.py | D | 04-Jul-2025 | 929 | 31 | 12 |
README.rst
1Run these examples from the root directory of pycparser. 2 3Please note that most realistic C code samples would require running the C 4preprocessor before passing the code to **pycparser**; see the `README file 5<https://github.com/eliben/pycparser/blob/master/README.rst>`_ and 6`this blog post 7<https://eli.thegreenplace.net/2015/on-parsing-c-type-declarations-and-fake-headers>`_ 8more details. 9