wave: #include with an empty file causes a crash under Windows

[anonymous]

If a file included with #include is processed by boost wave, it will crash with an access violation under Windows. It doesn't appear to crash under Linux, though it could still be an issue that just isn't bad enough to bring down the whole system.

The following is an example:

#include "Empty.h"

int foo()
{
    return 0;
}

Note that Empty.h must be completely empty, including no terminating newline.

[anonymous]

For some additional info, this was with Visual Studio 2015. Additionally, it doesn't crash in debug, but does crash on release.