C syntax highlighting.

If you write #include <float.h>.
It weirdly highlights the float part in blue, even though we are referring to the library not declaring a variable.

[JoeKar]

The same would actually happen, when the standard library header of int and bool would be int.h & bool.h instead of stdint.h & stdbool.h.
Currently the regular expressions checks for word boundaries, which it finds in case of <float.h>.

Fixing this might require a region to not break any other use cases.

@Andriamanitra:
Do you have a better idea than me?

[Andriamanitra]

This may not be a better idea but the simplest fix is to reset the highlighting just before the rule that highlights preprocessor directives:

- default: "^#include\\s+<.*>"

[JoeKar]

Also an option (+ additional spaces before and after #), even when it feels more like a workaround.
Something like...

    - preproc:
        start: "^\\s*#\\s*include"
        end: "$"
        rules:
            - identifier:
                start: "<"
                end: ">"
            - identifier:
                start: "\""
                end: "\""

...would require a fully working highlighter, since the "patterns" are applied once again, but shouldn't.

[JoeKar]

@himansh-dev
Why did you close your issue?
From my perspective it is valid to leave it open, till it is solved.

[JoeKar]

Well, we leave it open now, OK?