I'm sorry; I actually meant my advice quite sincerely, with the following reasoning:

Reading the error output of a compiler is one of those things that you learn in your first three months of programming a computer, and learning the typical function signature of main() is something you do in your very first C++ program. These skills have nothing to do with your environment; they're cross-environment C++ diagnostics skills. Other such skills include the ability to read and act on link errors; the ability to use a source level debugger; and the ability to introduce logging output in your program where necessary to diagnose a problem. I have no idea whether you have these or not, but they are other basic skills in the same category as the apparent omissions you demonstrated.

Drawing on experience tutoring other programmers, I concluded that you need more experience developing for C++, itself, before you actually start learning something "deep" using that language. If you feel you're better off doing both at once, that's of course your choice. If you have problems understanding specific language constructs or compiler or linker errors, then I suggest the For Beginners forum, which is an excellent place for that kind of question.

Good luck! (That's sincere, too)

Well as long as it is sincere [smile]. I will accept that I do not know what all of the errors mean, and I don't know very well how to convert code written in VC++ to DEV_C++, not even the basics of it. But I do know that my passion for programming will bring me further then writting simple programs using cout and cin. I know that I need more experiance, but I also know that what I do know is enough not to relearn the basics but missing a few "fundamental" aspecs. Truth be told, I am tired of reading, and I just want to get my hands into some "deep" coding. I am sorry though that because of my lack of a few important facts, I needed to waste peoples time on this forum, but I am still thankful for all the help.

Now if you don't mind, I (sincerly) think it is time to code. Then some sleep![dead]

Can't... sleep... must... code... :-)

On the bright side, when you switch environments once, you start learning first-hand the differences between a language (C++) and an environment (MSVC, DEVCPP, etc), which is one of the many steps towards becoming a skilled programmer.

I'd suggest going for Linux/automake next. :grin:

I really have been meaning to get my hands on a copy of Linux for a while... This conversation has been fun [lol] We must do this again soon. Thanks for the advice. Besides DEV_CPP I have used Rhide GNUCPP the DOS environment that came with one of the books I bought, I really didn't like the interface nor the debugger that came with it.