Codenizer

Codenizer is a tool for detecting possible problems (bugs) before script execution. It is used to pinpoint possible problematic locations which could eventually lead to bugs in the program -- while debuggers are used to eliminate bugs once they are in the program Codenizer is used to prevent bugs from appearing in the program in the first place.

Codenizer can help you dramatically improve code quality and allow you to do much more in less time. It has bunch of built-in checks for all kinds of usual errors which inevitably occur during development. With Codenizer you can focus on complex application logic rather than chasing simple bugs and typos. Codenizer is easily integrated into many different editors and integrated development environments, so you don't have to change your usual way of work.

You can find out more about Codenizer here. In section about Codenizer you can also find free version with limited functionality, but with bunch of very useful features still enabled, or you can buy full version from our world-wide retailer. If you have any question regarding use of Codenizer you can post it into our support center and we will come to you as soon as possible.

Codenizer can save you a lot of time on debugging, allowing you to focus on more complicated aspects of the problems you are working on. Codenizer's ability to assist you in code checking allows you to do more ACTUAL work on your program than before, in the same amount of time.

Codenizer is a software development tool designed to help you write better PHP code. Codenizer will take care of common programming mistakes for you:
• Uninitalized and unused variables
• Errors in function calls
• Unreachable code
• Performance issues
• Accessing undeclared object properties
• Calling undeclared functions
• Many other errors

Codenizer does its work by static analysis of PHP source you write, so it doesn't even require you to have PHP interpreter installed on your computer. Best of all Codenizer is setup within minute.

Benefits:
• Codenizer is able to execute actually rather modest set of PHP functions consisting of only two functions -- "dirname" (to allow you to include files giving absolute path), and "define" (to allow you to store something in constant and to use that later through your includes), however, most of PHP operators are supported in include expressions. Strictly speaking, calculating include paths is the only place where Codenizer will attempt to execute fragments of your code.
• One important thing to note is that Codenizer doesn't use the same parser as PHP interpreter but rather its own parser written from scratch especially for this purpose. What that means, and why is that important? Well, Codenizer will usually recover from almost any syntax error in your code and it will be able to report it to you and to happily continue parsing and analyzing code, although PHP interpreter would fail on first syntax error it encounters. There is one special case in which Codenizer does not report syntax error where it exists -- that is separating $ from variable name (for example '$ var'). Codenizer will silently accept this error and continue parsing without warning about it. On the other hand PHP parser will abort if you have something like this in your code no matter whether it would be within current execution flow or not.
• Codenizer will also complain about lots of things that are considered completely legal in PHP language (for example, calling non-static function in class as it was static, passing wrong number of arguments to function, accessing undeclared properties of objects and so on). If you rely on some of these 'features' then you should probably just ignore some of the messages Codenizer gives you :-)