Ok, don't get mad!!
I actually searched for my question and did not really find an accurate answer. I want to know how much c++ one should know before reading the win32, charles petzold book? I would like a more accurate answer, like the concepts that will be expected to already be known and not "good at c++" or some crappy answer. Do you just need to know cin, or cout, or link lists, templates, classes, or what exactly? Any educated response would be much appreciated. I'm debating if I should buy an intermediate c++ book or will I be ok to start on win32 api.
Just really need to be content with your c++ skills. The reason I got into Win32 programming is becuase I was bored with plain c++ ; I had learnt basically as much as I needed to know at the time.
If you are referring to 'Programming Windows' you don't need to know any C++ at all because the book is a guide to programming for windows using C. You can always adapt that information to use c++, if you so wish. The book is generally recommended as the one to own if you are doing any sort of win32 programming.
If you are interested in c++ book recomendations then do a search in all the boards for such; there was a longish thread in off-topic not so longs ago suggesting some excellent texts.
So I need to learn c before picking up a win32 book?
Petzold's Programming Windows is thorough and well enough written for just about anyone although it is aimed at msvc users ie if that's the compiler you are using then you should have few problems with the code examples which are provided on a cd with the book (cd also has an ebook version of the book). The code will generally work with few modifications if you are using another compiler such as mingw.
Regarding knowledge of c/c++, since c++ is often described as a 'superset of c' knowledge of one 'kind of' implies knowledge of the other. If your preference is for C, then go for C texts, if your preference is for c++ then go for c++ texts. If you want both then do both. Regardless of these choices, Petzold's book is still the number 1 recommendation for programming with the win32 api although the code examples are actually written in C. It has everything (except a compiler ;) ) to get you started 'Programming Windows with the win32 API'.
Mr. Petzold has another book with ISBN 0-7356-1370-2 Is this book more relavant in the job market than win32 programming? I mean if petzold is making the book and all that must mean something, right? Maybe he is just on MS payroll. Would anyone know if c# uses the win32 api? If it does then wouldn't it be better to learn win32 using c# than c?
Nope. Learn in this order:
My suggestion anyway. And just to let you know, learning Windows programming is a little like being a farmer: Don't plant your seeds in the morning and expect blossoms by nightfall. :) It's an uphill climb, brother.
You definitely need to have the basics down of either c/ c++ before starting win32 programming. You might as well start with c++, it's got some functionality that you'll learn to apprectiate that's lacking in c. So, learn c++, learn programming for the command line then make the jump to using the win32 API.
Just my $0.02
start with normal C++ until you get the gist of the sytax and keywords, like sizeof and others.
but win32 is VERY different, you dont use cout or cin anymore. so you dont need to know a whole crud load of normal c++ as its not really needed in win32 programming. as its almost all different.
so far, the only keywords ive really come across are
(a couple others, cant think right now). go with like, a week or two of console, then jump right on into windows32 programming. dont be afraid either.
Thanks for the response. I'm ok with c++. I mean I know most of the basics, classes, functions stuff like that, but am not good with pointers or anything complex ;-) It sounds like with a basic knowledge of c++ I will be ok jumping into win32 programming. Thanks again.
One more thing. I asked the c# forum about what is better, c# using the .net framework for windows developement or win32 for windows developement. Here is my response "C# does not use the WinAPI, it uses the .NET Framework which is a different set of classes not unlike MFC but a lot easier to use and more powerful."
The reason why I am asking about win32 or c# is because I want to know what would be better in for the job market. Any feedback on the more relevant of the two would be great.
>>The reason why I am asking about win32 or c# is because I want to know what would be better in for the job market.
I suggest you look on a employment site. Will vary from place to place.
Look for jobs you qualify for or are interested in.
Remember things like MFC use the WIN32 API and C# is relatively new.