Checking Deadlinks From the database manually is a Headache ,So why not use a script which return the http status of the particular link and tell us if the link is dead or not.So how do we check the dead links from the database ? How do we programatically check whether the link is dead or not ? To check broken or dead links from Database we will use curl .

Included in the post is a sample script that extracts the URLs from a field in the database (you'd need some extra smarts if you're pulling it from content) and running it though a "checklink" function. If the call to curl_getinfo returns false, the link is marked dead.

Recently I've been working on some new functionality to visualise all the code paths that make up each function. These new routines sit on top of the routines that do dead code analysis. These new routines sit on top of the routines that do dead code analysis. Every branch instruction (such as if, but also for and foreach) is analysed and a list of branches is created. [...] Once all the branches and their links are found, another algorithm runs to figure out which paths can be created out of all the branches.

He illustrates with a few examples, showing both the command that was executed and the resulting output with the new path information of a simple test file using a "for" loop and an "if/else" conditional.

I am a subscriber of International PHP Magazine for years. I bought the subscription looking at the back issues. They were sexy, resourceful and yup, very good. But I think these guys don't care about the magazine anymore. It became just a funny stuff for them. All the readers/subscribers and viewers doesn't bring any value to them. Look what they are doing actually...

He points out six things that the magazine and its staff are doing including RoR articles in an issue, content on the site that's way out of date and the smaller size of recent issues. Comments to the post point out that there has been issues released but that the magazine is published by a non-technical company that just might be pushing this particular publication aside.

A friend recently told me that PHP is on its way out, Ruby on Rails is where it's at. I scoffed. I chuckled. Then I gave it some thought. Could PHP have had its day?

[After my research] I have to conclude that my friend might be right in one respect - PHP has had its day. If the trend continues, it means that PHP will one day not be the hottest thing on the web like it is right now.

He's not abandoning ship just yet, though - he notes that:

PHP still has plenty of legs, and it will take quite a bit to wind it. I'm not sure what will take its place, but somehow I don't think Ruby on Rails will be the successor. PHP's advantage over the rest is that it's a web application, through and through. It doesn't try to also be a desktop application language, a server application language, a widget application language... it just spits out web pages fast and efficiently.