IDE recognition of _Static_assert

[Brian H]

The STM32 compiler toolchain supplied with CubeIDE 1.13.1 recognizes the _Static_assert statement, but the IDE itself does not (it marks it as a syntax error).  Can this be fixed?  Is there a setting I can change in the IDE to stop flagging _Static_assert as a syntax error without turning off all syntax checking?

Image showing IDE highlighting _Static_assert statement as a syntax error:

Image showing correct compiler treatment of _Static_assert:

To be clear, this is not a show-stopping problem; it's just an annoyance factor.

[TDK]

Where is _Static_assert  defined? The IDE needs to know about it and see the appropriate headers before the statement. Sometimes rebuilding the index can be required. Project -> C/C++ Index -> Rebuild. If you hit F3 on it, does it jump to the right definition?

You can use static_assert instead, which the IDE will recognize.

[Pavel A.]

@TDK _Static_assert is a keyword in C11. (in same line as _Bool etc.)

[TDK]

Had no idea. I use C++ most of the time and there it's static_assert.

I see that in C23 _Static_assert is deprecated in favor of static_assert.

FWIW, my STM32CubeIDE recognizes _Static_assert as a keyword.

[Pavel A.]

Really... why the OP won't just include <assert.h> and use static_assert ...

Eclipse parser should ignore unknown stuff in system includes.

[CTapp.1]

The behaviour is the same for static_assert() and _Static_assert(), but it only happens when they are used at file-scope.

It looks as if the parser does not like function call syntax at file-scope - but they all compile as expected.

I would like to use them at file scope to check things like alignment and sizes, but I am going to have to move them into a "random" function if I want to get rid of the error markers.

Edited to fix typo

[Pavel A.]

Which C language standard is selected in your project settings?

(C/C++ build -> Settings -> MCU GCC Compiler-> General )

Try c17 or gnu17.

[CTapp.1]

Thanks, but that gives exactly the same results as C11 (as expected, really).

This looks more like an issue with the Eclipse CDT parser.

[Pavel A.]

@mattias norlander  #bugreport  Should this already work in the upstream CDT?

[Radosław]

In Project --> Properties --> C/C++ General --> Preprocessor Include Paths, Macros etc. add (as a USER ENTRY) an empty macro definition like
_Static_assert(a,b)
On the Entries tab, select CDT User Setting Entries
then click Add...
and pick Preprocessor Macro in the drop-down