Warning Directive
The most useful command, by far, this group is the command # warning. By codifying add TODO comments you find all the code, especially if developed in a team environment. These comments are useful when you want to remember to add more functionality to that piece of code. However, no good if in the end only to forget to do a search of all to an end. The command # prevents you from forgetting notice inserted on the right of command in the warning window to compile the code.
It is important to add yet EVERYTHING in the text to enable easy searching for them when they are outside the main code editor, or by people who are not familiar with the # warning directive.
Example
If you want to see the real warnings, then click the Header Description Sort by description. Then all the warnings # are grouped at the top or bottom ready to return later.
The # error directive is only useful if you have to remember to do something else before compiling your application as it will stop the compilation process and marks an error.
Example
To see the actual errors, then click the Header Description Sort by description. Then all the errors error # will be grouped at the top or bottom ready to return later.
The line directive has many possible uses, the most useful of them allows you to hide code debugger. This allows you to concentrate on a particular part of code during debugging.
The line directive has many possible uses, the most useful of them allows you to hide code debugger. This allows you to concentrate on a particular part of the code while debugging




0 comments:
Post a Comment