[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 Sergey Kalinichev changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #15 from Pedro Ferreira --- Created attachment 97352 --> https://bugs.kde.org/attachment.cgi?id=97352=edit Extension-based parsing Hi Sergey, I took a stab at fixing this one a while ago (patch attached) but did not

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #14 from Sergey Kalinichev --- Ok, I'm going to look into it. Still I don't really see an easy way to integrate this feature in the UI. E.g. should it be something like adding 2 options: C++ profile: ... C

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 Kevin Funk changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #12 from Pedro Ferreira --- The following review request refers to this bug: https://git.reviewboard.kde.org/r/127027/ This needs to be fixed before a unit test can be added to the feature implemented by the review

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #13 from Kevin Funk --- Git commit b930278bb44b37742bcbc19b12efeeb8026e1a3a by Kevin Funk, on behalf of Pedro Ferreira. Committed on 10/02/2016 at 16:21. Pushed by kfunk into branch '5.0'. Add support for

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #11 from Milian Wolff --- Sergey, can you look into this issue? -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #8 from Pedro Ferreira --- (In reply to Sergey Kalinichev from comment #7) > Yes, we can definitely parse .c as plain C. But then again it solves nothing > IMO, as people will come back complaining that headers are not

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #9 from Sergey Kalinichev --- > but .h files are parsed as part of #include directives. When compiling yes, but inside IDE not necessarily (e.g. you can add a header file and work on it, and #include it later

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Target Milestone|---

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #4 from Kevin Funk --- Git commit e15e93ee159c460bb67800ba94eb36f3f118ec67 by Kevin Funk. Committed on 06/01/2016 at 13:40. Pushed by kfunk into branch '5.0'. Clang: Add test case for pure C file Expected fail atm, but

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 Kevin Funk changed: What|Removed |Added Keywords||release_blocker --- Comment #2

[kdevelop] [Bug 357615] C file parsed as a C++ file

https://bugs.kde.org/show_bug.cgi?id=357615 --- Comment #3 from Kevin Funk --- Whoops. s/{};// in above comment. (That was a debugging aid added by me) -- You are receiving this mail because: You are watching all bug changes.