Server Help

[50% Packetloss]

I've been learning some of the basics of the Windows API from http://www.winprog.org/tutorial/ and ran across some stuff I hadn't seen before.
One of which is the GlobalAlloc() function, is this function any different or more efficient than malloc()? Also the CreateFile() function, is this any different or more efficient than fopen(). Both functions can be found under the Reading/Writing Files section of http://www.winprog.org/tutorial/app_two.html

I plan on reading more and placed an order for this book at Borders Books (a book store that works with or is owned by amazon)
Programming Windows, Fifth Edition
I'm not sure if its any good but it will take them 2-6 weeks to even get it in and I am interested if there are any other great books that I should start off with. I don't want to read any MFC crap or .net bullshit. So any help you guys provide is great.

I'm also learning some OpenGL with this book
Beginning OpenGL Game Programming
So far it seems to be a good read. I don't plan on writting any games but maybe some subspace dev software in the very distant future. Any recommended books would be a great help aswell.

[Mr Ekted]

They are both lower level (closer to the operating system). malloc() is a run-time function that ultimately calls HeapAlloc()--similar to GlobalAlloc(). fopen() is a run-time function that ultimately calls CreateFile(). If you want to write machine-independent code, you use the standard malloc/fopen calls which are supported by virtually all forms of C run-time libraries.

GlobalAlloc() doesn't actually return memory. It returns a handle to virtual memory. This means that there are some blocks of virtual memory set aside for you, but that have not been committed for access yet. GlobalLock() takes the handle and forces the memory--if necessary--into real physical RAM, returning the pointer. If you want to use the Windows clipboard functionality, you need to use the Global* family of functions, whose handles can be passed across processes.

CreateFile() can do all sorts of things that fopen() cannot, like pipes, sharing modes, and overlapped I/O.

[edit]

I really should not be saying physical RAM because it's all virtual. Address 0x00400000 for process A is not the same physical pointer as address 0x00400000 for process B.
_________________
4,691 irradiated haggis!

[Cyan~Fire]

Really, you don't need a book to write Windows code. I started learning from this. (I did have the "hard" copy in help form on my computer, though, which made it a bit easier.)

After you learn the basics and can make a window appear on the screen, check out some open source applications that use the API. For example, if you like AOK, check out my AOKTS source.
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[Mr Ekted]

Tsk tsk. Not only returns in the middle of functions, but returns instead of breaks in switch statements!

[50% Packetloss]

Thanks ekted, do you know of any good books that I should purchase?
_________________
Current Terror Alert Level

[Mr Ekted]

Understanding any aspect of Windows programming is much better with google than any book. You get good API reference, pages with overviews, and some sample code. The reference that comes with Visual Studio is pretty much vertabim from Microsoft's website.

[Cyan~Fire]

[xrestassuredx]

I occassionally run across a good book that actually does a good job of explaining things with decent examples. If you want to learn MFC, for example, Programming Windows with MFC (2nd Ed.) by Jeff Prosise is one of the best resources I have found, over googling for disparate and often inelegant code examples online.
As far as API programming, I try to stay on as high a level as possible (a software engineer's job description is to be lazy), so I can't help you there. If you are looking for books, though, go to a physical bookstore and look at the books you are buying to see how useful they really will be to you. You can usually find something that will work on google, but not always the "correct" or preferred solution to a problem that you would get from a well-written book.
_________________

[Mr Ekted]

[Dr Brain]

That's why CS people don't program embedded systems. That's what computer engineers are for. Programming hydraulic control systems.
_________________
Hyperspace Owner

Smong> so long as 99% deaths feel lame it will always be hyperspace to me

[SamHughes]

[Cerium]

That guy needs to be set on fire...twice.
Once for knowing the names numerous pokemon, and a second time for using them.

[Cyan~Fire]

I see nothing wrong with writing your own personal "library" of wrappers that you can use in any application you write. But relying on something like STL and having no clue what's actually going on behind the scenes 1) will make your programming very inefficient and roundabout, and 2) will SUCK for debugging. (Debugging is the primary reason I stopped using STL.)

Naming variables with crappy names is the least of my worries. And of course the friend commented his code up the wazoo, I guess to make sure I understood everything OK.

[xrestassuredx]

[Mr Ekted]

Programmer is the entry level position, almost clerical. Here's a spec, do this. A software engineer takes an idea and figures out how it's going to work, how it's going to be put together, where the critical areas are, designs it. I realize this is all just semantics, but be careful what you call yourself depending on who you talk to; it might affect the way they evaluate your skills.