[Scummvm-devel] Header files.

[Nicolas Noble]

> Yes, this is what I keep hearing, but I've not yet heard any
> detailed explanation of how this "strange behaviour" manifests
> itself.  What, exactly, happens if you add
>
>   #include "foobar.h"
>
> where foobar.h is an empty file, before the include of "stdafx.h"?

IIRC, it just complains out loud, and stop compiling.

> I'm curious how anyone could make a C compiler that would break on
> something like that.

The answer is near "Where do you want to go today?"