Yes it is. I've been programming C/WinAPI for about 7 years now and it *still* overwhelms me. Hey, between the Windows API, Pelles C (with it's expanded library), Direct X, SDL and a couple of others, we're looking at very near 50,000 function calls! This is where one either gets real good at "looking stuff up" or finds a new career... :D
Originally Posted by jhilory
Nope it's all there.
I followed your suggestions in an earlier post and downloaded and installed the Windows SDK (it's 1.4 GB!), then downloaded and installed the Win98SDK from the Pelles C site. I got it linked into Pelles C, such that F1 does bring up API references. It appears, however, that it is mostly "Windows 95" and older, I found some of the help for APIs, that I was trying to use, was missing. When you say "fully documented", is there something other than the help file, that I may be missing?
Pelles help file is a full disclosure of his toolchain, IDE, C-99 and libraries. There's even a mini-tutorial in there.
The SDK version I linked to is the last version that installs the Windows API reference directly on your hard disk. It's current to Win7 sp1. All newer versions link to their online reference... which mean's you're dinked if you don't have Internet access at the moment. Hense my recommendation for that version.
The Win98 sdk that comes up from F1 is old, but still perfectly valid and useable... about 90% of the Win7 Api is covered in there, but it really only for "quick reference"... the SDK should be the final authority on what's current and what's not.
Between those files you have pretty much the whole schebang.
Think of it as an opportunity for professional growth... Especially important since the world is moving to 64bit processing and most amd64 OSs will not even run 16 bit code anymore...
I hear what you are saying, and I have not, really, buried my head in the sand. I'm just trying to understand some of the Windows concepts, enough to get something up and going. Later, after more experience, I can start thinking more about "is there a better way?".
Believe me, you will learn real fast when you have to use CreateFile(), ReadFile(), WriteFile() and CloseFile() with your com ports... THAT is an education in and of itself...
Right now, I don't know enough about Windows programming and its basic concepts to undertake a full rewrite.., maybe later. Most of my code is pretty straight-forward -- receiving a serial data input, converting hexidecimal input chars, getting everything in the proper structure (byte, word, etc.), and writing it all to several CSV files for later database input. This is already written in C, and not much required to move it into Pelles C. This program is called by Windows' Scheduler on a periodic basis to collect data from several different sources. My original program is written to work with COM1 and COM2 (the std PC COM ports), but now, since PCs don't come with any COM ports, I was faced with making changes to handle any higher-numbered COM port, virtual or otherwise, and, eventually, ethernet. That is what spurred my interest in moving my program into a Windows environment.
Hey... I know exactly what you're saying... I keep going off to try wonderful new languages and compilers, I discover some of the niftyiest stuff (Like D and HLA) but no matter what I do, I somehow always wind up back on Pelles C... And to be honest, it's mostly because of POIDE and it's various facilities; help file, resource editors, etc.
I have Windows 8 Developers Preview installed on one machine, and it came with Visual C++ 2011 Express Edition Preview. I have played around with it a little, and it makes me like Pelles C even more! Thanks for turning me on to Pelles C!
If you check into the Pelles C forums... Pelles C forum - Index ... you will discover a very competent and helpful crew of people. You will also discover AddIns, Wizards and Libraires that you can download... You might even recognize one of the authors :D ...
I'm glad its working out so well for you!