<?php

function assert_failed($file, $line, $expr) {

    print "Assertion failed in $file [ $line ] : $expr <br/>";

}

//error_reporting设置为0, 相当于调用assert_options(ASSERT_WARNING, 0);

//error_reporting(0);

//是否启用对ASSERT_ACTIVE的支持

assert_options(ASSERT_ACTIVE, 1);

//是否在发送第一次wanning的时候,停止脚本的执行

assert_options(ASSERT_BAIL, 0);

//没搞定,还不明白具体怎么用,偶测试不出来

//assert_options(ASSERT_QUIET_EVAL, 0);

echo "step 1 <br />";

assert(1==1);

echo "step 2 <br />";

assert(2==1);

echo "step 3 <br />";

//设定assert的callback样式,可以自己定义wanning信息显示时的样式

assert_options(ASSERT_CALLBACK, 'assert_failed');

//不显示assert()自己产生warnning信息，如果设置了ASSERT_CALLBACK，仍然还会显示ASSERT_CALLBACK函数对应的信息，但是函数中传入的$expr参数不起作用.

//assert_options(ASSERT_WARNING, 1);

assert(1==1);

assert((1/0)>2);

echo "step 4 <br />";

?>

The assert( ) function is a clever one  
that works along the same lines as our print statements, but it only works if a certain condition is not matched. Essentially, assert( ) is used to say "This statement must be trueif it isn't, please tell me." For example:

    print "Stage 1\n";

    assert(1 =  = 1);

    print "Stage 2\n";

    assert(1 =  = 2);

    print "Stage 3\n";

Here we have two assert( )s, with the first call asserting that one must be equal to one, and the second call asserting that one must be equal to two. As it is impossible to redefine constants like 1 and 2, the first assert( ) will always evaluate to true, and the second will always evaluate to false. Here is the output from the script:

    Stage 1

    Stage 2

    Warning: assert( ) [http://www.php.net/function.assert]: Assertion failed

            in /home/paul/sandbox/php/assert.php on line 5

    Stage 3

The first assert( ) is not seen in the output at all because it evaluated to TRue, whereas the second assert( ) evaluated to false, so we get a warning about an assertion failure. However, script execution carries on so that we see "Stage 3" after the assertion failure warning. As long as assertions evaluate to true, they have no effect on the running of the script, which means you can insert them for debugging purposes and not have to worry about taking them out once you are finished debugging.

If you are worried about your assertions slowing execution down, which, although the speed hit will be minimal, is still a valid concern, you can disable execution of assert( ) by using the assert_options( ) function or by setting assert.active to Off in your php.ini file. If you want to use assert_options( ), it takes two parameters: the option to set and the value you wish to set it to.

Table 22-1 shows the list of options you can use for the first parameter of assert_options( ):

Table 22-1. First parameter of assert_options( )

Parameter          Default    Description

ASSERT_ACTIVE      On         Enables evaluation of assert( ) calls

ASSERT_WARNING     On         Makes PHP output a warning for each failed assertion

ASSERT_BAIL        Off        Forces PHP to end script execution on a failed assertion

ASSERT_QUIET_EVAL  Off        Ignores errors in assert( ) calls

ASSERT_CALLBACK    Off        Names user function to call on a failed assertion

To disable assert( ) calls, use this line of code:

    assert_options(ASSERT_ACTIVE, 0);

And to make PHP end script execution rather than just issue a warning, we can use this line of code:

    assert_options(ASSERT_BAIL, 1);

Note that all of these options can be set in your php.ini file so that they are always in effect. The options to change there are assert.active, assert.warning, assert.bail, assert.quiet_eval, and assert_callback.

ASSERT_CALLBACK is a useful option, as it allows you to write an error handler for when your code fails an assertion. It takes the string name of a function to execute when assertions fail, and the function you define must take three parameters: one to hold the file where the assertion occurred, one to hold the line, and one to hold the expression. Using all three together in your callback function allows you to generate meaningful error messages that you can debug. For example:

    function assert_failed($file, $line, $expr) {

            print "Assertion failed in $file on line $line: $expr\n";

    }

    assert_options(ASSERT_CALLBACK, 'assert_failed');

    assert_options(ASSERT_WARNING, 0);

    $foo = 10;

    $bar = 11;

    assert($foo > $bar);

That example shows a callback function defined that takes $file, $line, and $expr for the three variables passed in, and outputs them whenever an assertion fails. To make that result actually happen, assert_options( ) is called to let PHP know that assert_failed( ) is the correct function to use as a callbacknote that there are no brackets after the string being passed into assert_options( ).

ASSERT_WARNING is also disabled, which stops PHP from outputting a warning as well as running the callback function. Finally, two variables are set, and are used as part of a call to assert( )as you can see, $foo is quite clearly not greater than $bar, which means the assertion will fail and call our callback. So, the output from the script is: Assertion failed in /home/paul/tmp/blerg.php on line 9: $foo > $bar.

You can assert( ) any statement you like, as long as it will return either TRue or false. This makes the assert( ) function incredibly powerfuleven more so when you think that you can just turn off assertion execution to make the code run at full speed.

Here are some more examples of assert( )able things:

    assert($savings >= $salary / 10);

    assert($myarray =  = array("apone", "burke", "hicks"));

    assert(preg_match("/wild sheep chase/", $book));