Am 22.08.2012 09:45, schrieb Lester Caine:
Personally I'm looking for a 'Official Userland Library' that provides EXAMPLES of how to do operations rather than yet another downloadable library. Something I can cut and past from into my own code when I need a widget and which provides a much more 'PHP approved' style to the code I'm using now. Putting this into PEAR is most definitely not what I need. I need to be able to see the code on-line.
I guess as always, the deployment of this userland-library depends on the php-users personal preference. I agree with Lester in that I'd rather have it available online as a proven example of how to solve a very specific problem instead of loading yet another bunch of functions I might not even need, just for the sake of having them.
But I guess we could have both. I am not sure we should have a hefty namespace attached to those functions though...it would of course make the situation of naming clashes less dire, but that could also be solved manually by copy/pasting and then renaming according to taste.
This is the beauty of it all. Wether you want to make the functions available globally, grouped as a static class or using namespaces is left to the user.
Making the "Library" available for download as a complete package or using PEAR/Composer could be a second project, no? Lets focus on how it could fit into the manual (or not) and then go on to how it could be served as a package?
I'd really like some comments/thoughts from a php-dev on this...and maybe someone from docs?
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
