pearAstonishing. I’m quite surprised. I thought PHPUnit was fairly well integrated into PEAR (pear run-tests). I’m not sure if this is a fork, or if PEAR will continue to use PHPUnit as an external dependency?
I’ve never been a PEAR fan. My experiences being peripherally involved with the XML_HTMLSax package weren’t [...]
It looks there is a Mambo worm out now. I read Hackers Hitting Popular Apps a couple of weeks ago and it mentioned that hackers are targeting PHP apps among other things. Dog bites man for some. More interesting was this quote:
“The bottom line is that security has been set back nearly [...]
I guess I missed the Zend PHP Framework webcast on Friday. I was looking forward to it, but I signed up a while ago and forgot about it. By the time I got the reminder email, it was too late. Fortunately, the recording is now available. If you have an interest [...]
I am very interested in the new PEAR channels. I like where this is going. I especially like the idea of web application installers (versus library installers).
I wish i could just do:
pear install Calendar beta
instead of:
pear config-set preferred_state beta
pear install Calendar
pear config-set preferred_state stable
I have to disagree with Paul Jones on coding standards:
The thing about defining a coding style standard is that there is no objective means by which to judge one style as “better†or “more-right†than another.
I can think of several objective criteria for judging coding standards practices off the top of my head:
Does the practice [...]
Alan Knowles has an update on the status of the template debate in PEAR. Alan chose to highlight a post by Hans Lellelid. I also had this message flagged for comment.
Hans makes the argument for a tighter vision for PEAR, as well as for an overflow method for packages that don’t [...]
Aaron Wormus blogs on PEAR Template trouble. The PEAR community seems to be having a significant debate over the proposal to include the template engine Savant into PEAR.
This proposal represents an identity crisis for PEAR. Joshua Eichorn recognizes the issue:
Either we have 1 engine and multiple api’s and fix mistakes of the [...]
Jon Ramsey came up with a continuous integration tool called Rephlux. Rephlux periodically checks out your code from CVS and runs your unit tests on it. It produces a RSS feed of test failures and a RSS feed of CVS revisions. How cool is that?
In the future it should be possible to [...]
All Posts
