PHP Lib Testing
Lately the PHP has gained a few units tests. I know usually the tests are done while the code is being developed and there is less to gain by writing tests after the fact, but the point it to help future development. The whole library is not completely cover by test cases, but it in progress. Currently, I received some consultant work to do and so increases the unit tests will have to wait a while.
PHP lib
I created a PHP library for my Master's PILOT and had been debating on whether to release it to the public in a GPL license. I finally realized that there are many others PHP libraries out there with many more features and proven uses and so the chances of my library being used in any significant way is small. So why release it then? It might teach someone something and would increase the quality of the library with potential public eyes on it. I spent some time creating a script that automatically creates an tarball of the latests version from the repository and can be found at download.whedimer.com/snapshot/wlib_php. Stable releases will eventually come.
Criticism on the library is welcome so long as the language used is civil and specific towards a particular aspect (no vague or general criticisms please). Keep in mind I have little professional experience and so keep your expectations low.
PHP Lib Fully Commented
The first round of commenting for the PHP library is now complete. More commenting is needed to bring it up the the standards that I think are nescessary to call the code "well commented". All the classes, instance variables, methods and functions have autodoc comments. For those who might wonder why the commenting is happening after the writing of the code, it was simply a matter of time. The code was written as part of my Master's project and so proper code standards were ignored to focuse on the problem I was working on. The same sort of thing will happen with automated testing, which is currently being worked on.