Monday, May 24, 2010

For visual c+ compiling, is there is a a way to determine an good why to find typo error.?

There are several editors that will point out syntax errors in the language.

For visual c+ compiling, is there is a a way to determine an good why to find typo error.?
I've never used anything other than the Visual C++ editor.


Yeah, there are a lot of other editors out there, but they pretty much do the same thing as far as finding typo errors.





The Visual C++ editor does a good job at helping find mistakes,


though it can't find, or figure out every mistake you make, whether


intentional or non intentional.





One more comment.


If you make a mistake while typing a function, such as sprint instead of sprintf, the editor doesn't necessarily know that you have made a mistake, because you might have created a sprint function in another file. The complier doesn't know this until it is compiled.





I would suggest that you slow down and look at what you are typing, rather than having something else find your mistakes.


Plus, you can compile every once in a while and find the mistakes on your own, that way it will teach you to keep making the same mistakes.


No comments:

Post a Comment