>> but it complains at compile time.
Without seeing a lot more of your code it is not possible to tell what you need to do. Also don't post messgages about compile errors without posting the error message and the line of code it points to and any associated information to explain that line of code (like function signatures).
>> but I also learn quick.
I don’t care how fast you learn, these days there are thousands of people out there inventing new stuff faster than you can learn. And by the time you started there was already more stuff than you could ever learn.
Teach yourself C++ in 21 days That is just ridiculous. You can’t teach yourself VB in 21 days let alone C++. I wouldn’t touch that book with a ten foot pole.
The thing is, even if you manage to copy some code and get it to work, if you don’t understand what is happening then you have not really learned anything. Be patient, it takes everyone time to learn C++ I’ve been a C++ student for 14 years now!
Perspective, I just interviewed a fellow last week that had 8 years experience and
C++ expert on his resume. I have interview questions for C++ ranging from a 2 to 7 on a scale of 1 to 10 with 10 being an expert of course. He couldn’t answer a single 3 question, nor white board a single line of code without a compile error. I have interviewed between 40 and 100 candidates in the past 10 years and about 4 of them had anywhere near an accurate assessment of their level of knowledge of C++. The reason my questions stop at a rating of 7 is because it is a stretch to consider myself a 7 on a scale of 1 to 10 and in fact I don’t , I’m about a 5 or maybe a 6. My questions go to 7 to give people the benefit of doubt.
Ouch… damn, fell off my stump… hey where did everyone go?
-pete