BUG: Spaces Preceding Header File Name Generate Build Errors

• Microsoft Visual C++ for Windows, 16-bit edition, versions 1.0, 1.5, 1.51
• Microsoft Visual C++, 32-bit Editions, versions 1.0, 2.0, 2.1, 4.0, 4.1, 5.0

SYMPTOMS

The following dependency scan errors and/or compiler C1083 errors are generated when you attempt to scan dependencies or compile a header file that contains an #include directive with leading spaces in the file name:

• Scanning dependencies on a header file included in your source file may generate the following error if the header file name contains leading spaces:

  Could not find the file FILENAME.EXT

  Here " FILENAME.EXT" is the name of the included header file.



• Attempting to compile a source file that includes a header file with leading spaces in the file name generates this compiler error:

  Fatal error C1083: Cannot open include file: ' FILENAME.EXT' : No such file or directory

  Here " FILENAME.EXT" is the name of the included header file.

RESOLUTION

Delete the space(s) preceding the filename in the #include directive.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

In the 32-bit versions of windows, spaces are valid characters in the file names. This is by design in the 32-bit versions of Visual C++.

MORE INFORMATION

To reproduce this error, create a text file called TEST.H and include this file in your source file with this statement:

   #Include " TEST.H"  // Note the space between quotation mark (") and    TEST.H 

Additional query words: kbVC400bug 8.00 8.00c 9.00 10.00 10.10 10.20

Keywords : kbCompiler kbide kbVC kbVC500bug
Version : WINDOWS:1.0,1.5,1.51; winnt:1.0,2.0,2.1,4.0,4.1,5.0
Platform : WINDOWS winnt
Issue type : kbbug