Reproduced C++assert () function

The prototype of an Assert macro is defined in <assert.h>, and its function is to terminate the execution of the program if its condition returns an error, and the prototype defines:

< assert.h > void  int  expression);

The function of an assert is to evaluate expression expressions, if the value is False (that is, 0), then it prints an error message to stderr and then terminates the program by calling abort. Take a look at the following program listing BADPTR.C:

#include <stdio.h> #include <assert.h> #include <stdlib.h>int main (void) {       FILE *fp;           fp = fopen ("Test.txt", "w");//Open a file in a writable manner and create a file       assert (FP) with the same name if it does not exist;                       So there's no error here       . fclose (FP);           fp = fopen ("Noexitfile.txt", "R");//Opens a file in a read-only manner, and if it does not exist, the file fails       assert (FP);                       So here's the error       fclose (FP);                       The program will never execute here to       return 0;}

[Email protected] error_process]# gcc badptr.c
[Email protected] error_process]#./a.out
A.out:badptr.c:14:main:assertion ' FP ' failed.

The disadvantage of using assert () is that frequent calls can greatly affect the performance of the program and add additional overhead. After debugging, you can disable the Assert call by inserting the #define NDEBUG before the statement that contains # include <assert.h>, as shown in the following example code:

#include <stdio.h> #define Ndebug#include <assert.h>

Usage Summary and Precautions:

1) Verify the legitimacy of incoming parameters at the beginning of the function, such as:

int resetbuffersize (int nnewsize) {//function: Change buffer size,//parameter: Nnewsize buffer new Length//return value: Buffer current Length//Description: Keep the original information content unchanged     nnewsize<=0　　Represents the purge buffer assert (nnewsize >= 0);　　ASSERT (Nnewsize <= max_buffer_size); ...}

2) Each assert examines only one condition, because when multiple conditions are checked, if the assertion fails, it is not possible to visually determine which condition failed, such as:

Not good:

assert (Noffset>=0&&  noffset+nSize  <=m_ninfomationsize);

Good:

>= 0 ); assert (Noffset+<=  m_ninfomationsize);

3) You cannot use a statement that alters the environment, because assert only takes effect in debug, and if you do, you will use the program to run into problems when it is actually running, such as:

Error:

assert (I+ +<);

This is because if there is an error, such as i=100 before execution, then this statement will not be executed, then i++ This command will not be executed.

That's right:

<  - ); I+ +;

4) The Assert and subsequent statements should be empty lines to form a logical and visual sense of consistency.

5) In some places, assert cannot replace conditional filtering.

       Assert is used to avoid obvious errors, not to handle exceptions. Errors and exceptions are not the same, errors should not occur, exceptions are unavoidable. C language anomalies can be handled by conditional judgment, and other languages have their own exception handling mechanisms.

       A very simple rule of using Assert is that, at the very beginning of a method or function, if you use it in the middle of a method, you need to consider carefully whether it should be. At the beginning of the method, a functional process was not started, and the problems that occurred during the execution of a functional process were almost abnormal.