Userland API leveraging the 'php' namespace
| From: | Thomas Gossmann | Date: | Sun, 01 Jun 2014 16:56:27 +0000 |
| Subject: | Userland API leveraging the 'php' namespace | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-74668@lists.php.net to get a copy of this message | ||
Hello,
this is my first post to this group, so I hope this is the right place.
One day, I started working on an API, which I thought, would be cool to be the official php API. I was roughly adding some code together to imagine how this API will look like (nothing which would need to working for that case). I considered this as a huge playground for me. Lately I thought, this is worth sharing with others and from the early feedback, I'm not alone ;)
The idea is to work on a polyfill changing the userland API with the goal to make it official when the polyfill is stable. So, I wrote some lines together and shared it at PHP-FIG first (a couple of weeks ago).
Here are the goals for this project:
- Standardize function calls
- Wrap 'resource' types in classes
- Provide php functionality in an OOP fashion
- Add missing langauge features (hint collections)
- Primitives as Objects
- Offer more type hinting
More details on the repo and the readme:
https://github.com/gossi/oophp
In this mailing-list I also see similar requests and also found references to what I had in mind, which I collected at the repo.
For now, I'd like to hear your feedback about this and how to possibly proceed further with this.
Thank you very much
gossi