That's one of my favorite "forgots".Originally Posted by MacGyver
And the way I've come to find even better results lately is to search for "<stuff> site:msdn2.microsoft.com".I'm sure that's quite commonly noticed. Way to really find something on MSDN is to query the function name in google with "MSDN" somewhere in the search string.
So do other editors' tools.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
Where Win32 is the keyword...Code:Win32 site:msdn.microsoft.com
Thank you for posting I think i shall begin memorising (try to atleast (= ) the libraries you mentioned. If I ever get an understanding of those ones I shall move on to going through the rest. Thank you again for your time (=
I noticed my threads always get atleast 15 replys (= I need to come up with harder questions now to keep that up! (=
Y'arrh, Stop the smilies, it's very hard to read your posts.
This better )=
:P
Well alright if you insist
Lol smiles look better in posts
BTW this may be my 1000th post but I had loads more untill the boards crashed, as many of you may well remember
Double Helix STL
Congratulations again then!
I agree, but )= and (= is cryptic
I'd go the other way round. I remember the functions I need, and then what header I have to include for them.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Ahh a backwards man... Logically that is better
