{"comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/9d9434407b38d995c43ceb59fe6adb5b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"9d9434407b38d995c43ceb59fe6adb5b","url":"https://api.github.com/users/jalperin","login":"jalperin","id":129638},"position":5,"updated_at":"2011-11-17T17:39:24Z","commit_id":"65a9054d3ea639dda140e580242b120edb03ec4a","url":"https://api.github.com/repos/pkp/pkp-lib/comments/728142","line":47,"body":"This is childish. Florian, this is not your project anymore. I don't see why you care. Alec, you made a decision. It's done. Let's move on. \r\n\r\nOn 2011-11-17, at 9:34, jerico-dev<reply@reply.github.com> wrote:\r\n\r\n> You mean when users downgrade their servers to PHP4? That must happen quite often these days... That's a convincing argument. :P Requirements checking is done in filters at runtime whenever they execute. That's why it shouldn't pop up here. At least that was the intention that I wanted to document here. If your intention is to use this class differently and you want the end user to be confronted with this error message then using a fatal error here is adequate. I don't believe this is a good way to deal with installation requirements, though.\r\n> \r\n> --- \r\n> Reply to this email directly or view it on GitHub:\r\n> https://github.com/pkp/pkp-lib/commit/65a9054d3ea639dda140e580242b120edb03ec4a#commitcomment-728131","html_url":"https://github.com/pkp/pkp-lib/commit/65a9054d3e#commitcomment-728142","id":728142,"path":"classes/webservice/XmlWebService.inc.php","created_at":"2011-11-17T17:39:24Z"}}