https://bugs.kde.org/show_bug.cgi?id=394200
Bug ID: 394200
Summary: #include and #<whitespace>include are not handled
identically by the parser
Product: kdevelop
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
Hovering over `#include "foo.h"` will open a tooltip with a link to open foo.h
; not so when there's whitespace after the hash (`# include "foo.h"`). Both are
valid syntax; is this difference in behaviour a bug or a feature?
--
You are receiving this mail because:
You are watching all bug changes.
