Copyright (c) 2013-2021 Altenwald Solutions, S.L.
Authors: "Manuel Rubio" (manuel@altenwald.com).
PHP Interpreter pure 100% Erlang. This interpreter was made for enhance and give flexibility to projects that requires an interface for plugins or addons without new compilations.
In the same way, you can use for server PHP pages in an easy way.
The port is not 100% complete, please refer to compatibility table.
IMPORTANT
the generation of the documentation is made using edown which isn't compatible with OTP 23 and OTP 24 at the moment. If you need to generate the documentation, install an OTP 22 and run make doc removing the _build directory if you compiled previously with a more recent OTP version.
If you want to support the project to advance faster with the development you can make a donation. Thanks!
When I was leading a team of developers in Spain, in Telco companies the most in use language was PHP. Even for handling concurrency, they were using some techniques with POSIX mutexes, shared memory and nohup background processes. That was a nightmare.
We discover Erlang these days (back in 2009) and started to use it to solve all of those issues and create a more reliable software. But the rest of the companies and even our clients continued using and requesting to make changes using PHP. This way I discover that we could gave them the flexibility of PHP as logic language to develop their code and the reliability of Erlang virtual machine (BEAM).
We tried, however, to use previously other solutions like SpiderMonkey or V8 to use JavaScript like other projects do (Riak and CouchDB), but we realize those solutions create the dependency of an external library which isn't working as a breeze most of the times. And the requirement was about to use PHP and not other different languages.
The motivation was: have a 100% Erlang code PHP interpreter. No C extensions and trying to minimize as much as possible the dependencies to have as little as possible the interpreter. That's because JSON, MySQL and other extensions are in different repositories letting you to include them in your code or not, depending on your needs.
In 2016, after fight again and again against the same issue (heredoc), I decided to rewrite the parser in 100% Erlang code. This let me to get rid of neotoma and speed up a bit the parsing of the code. Indeed, this let me to solve the heredoc issue and continue implementing the rest of the PHP syntax easily.
In 2019, ePHP was published finally as a hex package. In addition, I developed a new library for Elixir which shows how to use ephp for Elixir projects and add the ability to use PHP templates for Phoenix Framework projects: ephp_template.
You can see even an example of ephp in use for the running on-the-fly of PHP code to play the Leprechaun game (source code here).
And a post to know how to write a stand-alone server with Erlang, without write a single line of Erlang code and using PHP for the logic of a XMPP component here.
ePHP requires to be run over an Erlang/OTP 19+, but not all the versions are full compatible or recommended. See the list:
| Erlang Version | Support | Notes |
|---|---|---|
| 24.0 | ✔️ | Recommended if you use OTP 24 |
| 23.3 | ✔️ | Recommended if you use OTP 23 |
| 23.2 | ✔️ | |
| 23.1 | ✔️ | |
| 23.0 | ✔️ | |
| 22.3 | ✔️ | Recommended if you use OTP 22 |
| 22.2 | ✔️ | |
| 22.1 | ✔️ | |
| 22.0 | ✔️ | |
| 21.3 | :heavy_check_mark: | Recommended if you use OTP 21 |
| 21.2 | ✔️ | |
| 21.1 | ✔️ | |
| 21.0 | ✔️ | |
| 20.3 | ❌ | fails in math lib |
| 20.2 | ✔️ | Recommended if you use OTP 20 |
| 20.1 | ✔️ | |
| 20.0 | ✔️ | |
| 19.3 | ✔️ | Recommended if you use OTP 19 |
| 19.2 | ✔️ | |
| 19.1 | ✔️ | |
| 19.0 | ✔️ |
A simple way to use, is include in your project rebar.config the following dependency line:
{ephp, "0.2.7"}And use the following code in your project:
{ok, Ctx} = ephp:context_new(),
PHP = "<? $a = 5 * 23; ?>Result for $a = <?=$a?>",
{ok, Text} = ephp:eval(Ctx, PHP).The result stored in Text should be:
Result for $a = 115
PHP has a lot of built-in libraries. This interpreter has a little implementation of them. You can see the functions in the compatibility table.
You can add your own functions specifying the PHP name, and the module and function, as follow:
ephp_context:register_func(Ctx, <<"time">>, ephp_lib_date, time).