Came from FB news feed. No back story though... I mis-copy/paste the title.

it can be common for a large project to generate such a large number of errors if someone forgets even a semi-colon, or to close a bracket, which is most likely the case.

My general rule of thumb is to ignore every error but the first one (or maybe the first couple, if a quick scan suggests they might stem from different causes). Errors in compilation tend to cascade, just as slicer4ever suggests, so a huge error list isn't exactly accurate information.

The warning list, too, might not be accurate since a warning generated in a header that is included multiple times will generate multiple warnings, and often you can eliminate a huge piece of your warning list just by fixing that one header.

I agree with all of the above. We couldn't really tell just by looking at the error and warning counts.

Overall, it's a nice humor.

With today's IDE with syntax highlighting and intellisense, I'm surprised that somebody are still making compile-time errors.

My intellisense-sense would start tingling as soon as nothing comes up when I expected it to come up.

It's most likely just missing references. It always looks a little scary when you build with a missing reference. Those errors add up very fast.

With today's IDE with syntax highlighting and intellisense, I'm surprised that somebody are still making compile-time errors.

My intellisense-sense would start tingling as soon as nothing comes up when I expected it to come up.

On a handful of projects I've been on I've turned off intellisense because it can be a real resource hog on some larger projects with atypical build processes.

It's most likely just missing references. It always looks a little scary when you build with a missing reference. Those errors add up very fast.

Ugh, aye, I hate it with C++ and headers when you make an error, and it gets reproted like 50 times because the file is included 50 times. Really VS? Can't you figure out it and group them already???

(that's on VS2008, mebbe 2010 already fixed that)

My Ogre build on the Mac gives 5-15k warnings in Xcode, all about visibility being changed or something. Not sure why and I don't really get XCode enough to care as long as the Mac port of my code runs. Ugh, Xcode's just foul after VC++.

With today's IDE with syntax highlighting and intellisense, I'm surprised that somebody are still making compile-time errors.

My intellisense-sense would start tingling as soon as nothing comes up when I expected it to come up.

Yeah, because intellisense (especially pre-2010) is known to work all the time and not delay itself for several minutes on non-trivial projects.