He is saying that to make an application, you have to read and learn about the microsoft windows API.
He is wrong, that API is not necessary to make a c++ program, it really depends on what you want to make, you could make your program only use the command line.
But some for some things, you do have to use the operating system.
like on windows, you have to use the WinSock API for sockets, and on unix, you use the Unix Sockets,
I'v found those two APIs to be quite similar, except for subtle differences, like for winsock, you have to call WSAStartup() once before you start using the library, and WSACleanup() when you finish, and in unix you dont do any of that.
also in unix you call close() and winsock you call closesocket()
another thing is that winsock does not support Raw Sockets.
I suggest you learn about the c++ language and its standard library and only once you know it a bit, start learning about specific APIs
I'v also found it quite nice to join an IRC channel about c++, normally people there can help quite a lot.
Join the Official SRL IRC channel. Learn how to Here.
Oh, I didn't really mean the API, but to start, I looked at Microsoft and some Google sites...
But the API is some kewl shizzle, can't doubt that.
The jealous temper of mankind, ever more disposed to censure than
to praise the work of others, has constantly made the pursuit of new
methods and systems no less perilous than the search after unknown
lands and seas.
A general rule of programming: The easier the language is to learn/read/understand, the slower it is. For example, SCAR is really slow. Pascal is faster than SCAR (talking about compiled code here). Java is faster than Pascal. C++ is faster than Java. Assembly is faster than C++.
Note that this general rule doesn't always hold true, but that's why it's a general rule, eh?
Interested in C# and Electrical Engineering? This might interest you.
There are currently 1 users browsing this thread. (0 members and 1 guests)