1
0
mirror of https://github.com/danog/PHP-Parser.git synced 2024-11-30 04:19:30 +01:00
PHP-Parser/README.md

101 lines
2.9 KiB
Markdown
Raw Normal View History

2011-05-31 18:01:00 +02:00
PHP Parser
==========
2016-02-20 21:53:08 +01:00
[![Build Status](https://travis-ci.org/nikic/PHP-Parser.svg?branch=master)](https://travis-ci.org/nikic/PHP-Parser) [![Coverage Status](https://coveralls.io/repos/github/nikic/PHP-Parser/badge.svg?branch=master)](https://coveralls.io/github/nikic/PHP-Parser?branch=master)
2016-07-22 17:07:56 +02:00
This is a PHP 5.2 to PHP 7.1 parser written in PHP. Its purpose is to simplify static code analysis and
2011-05-31 18:01:00 +02:00
manipulation.
2017-01-19 20:48:57 +01:00
[**Documentation for version 3.x**][doc_3_x] (stable; for running on PHP >= 5.5; for parsing PHP 5.2 to PHP 7.1).
2016-10-29 13:37:47 +02:00
2016-11-30 19:20:29 +01:00
[Documentation for version 2.x][doc_2_x] (stable; for running on PHP >= 5.4; for parsing PHP 5.2 to PHP 7.0).
2015-12-04 16:26:27 +01:00
2016-02-28 21:01:06 +01:00
[Documentation for version 1.x][doc_1_x] (unsupported; for running on PHP >= 5.3; for parsing PHP 5.2 to PHP 5.6).
2014-09-12 14:40:17 +02:00
2012-02-21 19:52:49 +01:00
In a Nutshell
-------------
2014-09-12 14:40:17 +02:00
The parser turns PHP source code into an abstract syntax tree. For example, if you pass the following code into the
parser:
2012-02-21 19:52:49 +01:00
```php
<?php
echo 'Hi', 'World';
hello\world('foo', 'bar' . 'baz');
```
You'll get a syntax tree looking roughly like this:
2015-06-26 00:30:22 +02:00
```php
2012-02-21 19:52:49 +01:00
array(
0: Stmt_Echo(
exprs: array(
0: Scalar_String(
value: Hi
)
1: Scalar_String(
value: World
)
)
)
1: Expr_FuncCall(
name: Name(
parts: array(
0: hello
1: world
)
)
args: array(
0: Arg(
value: Scalar_String(
value: foo
)
byRef: false
)
1: Arg(
value: Expr_Concat(
left: Scalar_String(
value: bar
)
right: Scalar_String(
value: baz
)
)
byRef: false
)
)
)
)
```
2012-02-21 19:58:11 +01:00
You can then work with this syntax tree, for example to statically analyze the code (e.g. to find
programming errors or security issues).
2012-02-21 19:52:49 +01:00
2012-02-21 19:58:11 +01:00
Additionally, you can convert a syntax tree back to PHP code. This allows you to do code preprocessing
(like automatedly porting code to older PHP versions).
2012-02-21 19:52:49 +01:00
Installation
------------
The preferred installation method is [composer](https://getcomposer.org):
php composer.phar require nikic/php-parser
2015-03-10 21:32:21 +01:00
Documentation
-------------
1. [Introduction](doc/0_Introduction.markdown)
2. [Usage of basic components](doc/2_Usage_of_basic_components.markdown)
3. [Other node tree representations](doc/3_Other_node_tree_representations.markdown)
4. [Code generation](doc/4_Code_generation.markdown)
2015-03-10 21:32:21 +01:00
Component documentation:
2016-10-29 13:37:47 +02:00
1. [Error handling](doc/component/Error_handling.markdown)
2. [Lexer](doc/component/Lexer.markdown)
2015-05-02 22:03:33 +02:00
[doc_1_x]: https://github.com/nikic/PHP-Parser/tree/1.x/doc
2016-07-22 17:07:56 +02:00
[doc_2_x]: https://github.com/nikic/PHP-Parser/tree/2.x/doc
2017-01-19 20:48:57 +01:00
[doc_3_x]: https://github.com/nikic/PHP-Parser/tree/3.x/doc
[doc_master]: https://github.com/nikic/PHP-Parser/tree/master/doc