Dirk Diggler
Pro
i dont know much about c++ but if its like other languages i've used, then u goto understand one thing:
when a program fails and tells you there's an error on line number 1000. that doesnt' mean the error actually exists on line number 1000. it only means it was at that point in the code that the program realized something is amiss.
so its now up to the programmer to sift through his code to determine where the fucck the problem is.
to avoid the hassle, i just usually add line markers to several chunks of my code.
I havent had this happen since I left college in 2000 when I was using the first version of Java wrinting programs in Notepad and running them from the command line. Compilers have come a long way, usually there is a few lines of code BEFORE that may need to be looked at but not more than 5-7 lines of code. Eg if you are thrown a NullPointerException at line 1000 and you declared the variable on line 995 but forgot to initialize it using new then yes this is true BUT the error isnt 500 lines away. If the compiler is complaining about a variable not being initialized I bet my paycheck the compiler will tell you the line where you declared it OR tried to use it before initializing it. For all the folks complaining about compiler errors being vague can you give me an example.
For all those complaining about Java you would hate classes in C/C++. Java makes things WAY easier and C# (even though less desirable by companies) makes things boat loads easier. All of your foundation in Object Oriented programming will come from your C/C++/Java courses once you understand the OO concept all of the other shyt should fall into place