IntelliSense errors with Parsing the .pb.h header file generated from the protobuffer proto file

[raholly]

Environment

• OS and Version: CentOS7
• VS Code Version: 1.98.2
• C/C++ Extension Version: 1.29.3

Bug Summary and Steps to Reproduce

Bug Summary:
Opening the .pb.h header file generated from the .proto file of Protobuf, there is IntelliSense error: this declaration has no storage class or type specifier.

1. My protobuf version is 3.6.0
2. The minimal case might look like this：

#include <google/protobuf/port_def.inc>
#include <google/protobuf/port_undef.inc>
#include <google/protobuf/port_def.inc>
PROTOBUF_NAMESPACE_OPEN
namespace internal {
class AnyMetadata;
}  // namespace internal
PROTOBUF_NAMESPACE_CLOSE

3. Error displayed on macro PROTOBUF_NAMESPACE_OPEN

4. The attachment here is the header file provided by protobuf
   protobuf-include.zip

Configuration and Logs

{
    "configurations": [
        {
            "name": "Linux",
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "cStandard": "c11",
            "cppStandard": "c++11",
            "intelliSenseMode": "linux-gcc-x64"
        }
    ],
    "version": 4
}

Other Extensions

No response

Additional context

No response

[bobbrow]

I can reproduce this on Ubuntu.

I'm not sure exactly what is going on, but the error clears itself with a trivial edit in the file (e.g. add a space). Since it sounds like this is a generated file, editing it is probably undesirable though.

[sean-mcmanus]

@raholly @bobbrow I've filed a bug on VS at https://developercommunity.visualstudio.com/t/C-IntelliSense-doesnt-redefine-macros/11021646 (we've had similar issues in the past with duplicate includes with macro defines, see #5182 , which got fixed ). The issue is caused by the way IntelliSense does "fragment" parsing and doesn't repro with the EDG compiler. The invalid error goes away when the automatic pch gets used. I believe VS also triggers some extra update by default which triggers the pch to be used sooner (so the error usually goes away after a few seconds unless auto pch is disabled), which we don't do.