>That has always been my biggest frustration with C or C++ - getting (redacted) to compile.
>The code can be perfect but you still receive 10,000 errors during compile because of some
>compiler switch. The build process can be as complex as the app. itself.


Visual FreePro will eventually include something called a Rapid Development Compiler which supports C and a subset of C++. It relaxes a lot of those error messages and provides source code level warnings instead (sort of like how NetBeans shows you things in code). It lets your code continue to run in the virtual machine even with errors in some places (where it can). When it comes to a place where there's a blocking error, it traps to the debugger so the user can fix it up. "Rapid Development" Compiler, or RDC.

A user recently posted that computers should make things easier for people. I agree.

What you're seeing there, Paul, is the throwback to the early days of compilers when memory was expensive. The header file definitions, include file requirements, etc., were to speed up compilation time. It's not necessary today. Many other languages have gotten rid of it. It's time the C and C++ standards do as well.