Ask the expert to help you debug the program

Program debugging is the process of testing the compiled program by manual or compiling the program to correct syntax errors and logical errors before putting it into actual operation. This is an indispensable step to ensure the correctness of computer information systems. After the computer program is written, it must be sent to the computer for testing.

The first step is to use the program to send the prepared source program to the computer according to a certain writing format, and Cheng He will add, delete or modify the source program according to the user's intention.

The second step is to translate the input source program into machine language, that is, use the compiler to perform a syntax check on the source program and translate the source program sentences that conform to the grammar rules into a "language" that can be recognized by the computer. If the compiler checks and finds a syntax error, the program must be used to correct the syntax error in the source program and then compile until there are no syntax errors.

The third step is to use the connection program in the computer to connect the translated computer language program and build it into a program that can really run on the computer. In the connection process, there is generally no connection error, if there is a connection error, it means that there are problems such as confusing subroutine calls or parameter passing errors in the source program. At this time, the source program needs to be modified with the program, and then compiled and concatenated, and so on until there are no connection errors.

In the fourth step, the modified program is tested and run, and the output results can be compared with the correct results of manual processing. If there is a discrepancy, it is an indication that there is a logical error in the computer's program. If the program is not large, you can use manual methods to simulate the computer to modify the data of the source program; If the program is large, it is obvious that manual simulation will not work, so the computer can only be set up to perform in a single-step manner, and track the operation of the program step by step.

Once you find the problem, you still have to use the program to modify the source program, and then you still have to compile, connect, and execute until there are no logical errors. It can also be compiled after it is completed.

<> I made an exact same mistake as yours, and I used the ** generated by vc6 and added two characters to it.

There was no problem with this project before it was added, but this problem occurred after it was added.

You should be able to see that I've added two to it"/"It's this line that is commented out that creates this problem, and you can add this line to your ** to solve your problem.

The reason is that the win32-based project in the VC needs some pre-compiled commands in this header file, and you can't remove it.

The 8-bit unsigned positive range is as follows.

Binary: 00000001 11111111 octal representation: Divide the binary from back to front in three digits as 00 000 001 11 111 111, and then convert each group into octal numbers as: 001 377 Hexadecimal notation: Separate the binary from back to front according to four digits as 0000 0001 1111 1111, and then convert each group into hexadecimal numbers as: 01 ff Similarly: 8-bit signed positive numbers range as follows.

Binary: 00000001 01111111 can be obtained by following the above method.

The octal system is: 001 177

Hexadecimal is: 01 7f

8-bit unsigned positive numbers representing the range 0a-a255, written as 00ha ha0ff in hexadecimal form; The representation range of 8-bit signed positive numbers is -128a a+127 written in 16-bit base form 80ha ha7f

Try it with iToa and Atoi functions, you can check the manual for details, it can support 2,4,8,16,10 base conversions, ready-made functions do not need to write programs; If you want to solve the problem by programming, you can convert it to str type first and then discuss it by bit.