https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #24 from Oliver Kellogg ---
Git commit 0372f89d7995a5fbc557e6c6090208bc54950e88 by Oliver Kellogg.
Committed on 10/09/2021 at 05:51.
Pushed by okellogg into branch 'master'.
Fix for "C++ importer does not recognize 'noexcept' keyword" :
li
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #23 from Oliver Kellogg ---
Git commit 3041141b10361aedb3c8c06c9ba36b5d25ac6f9a by Oliver Kellogg.
Committed on 13/05/2021 at 16:49.
Pushed by okellogg into branch 'release/21.04'.
lib/cppparser/lexer.{h,cpp} followup to commit 7d3eb05,
> F
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #22 from Oliver Kellogg ---
Git commit 7d3eb053739413a0eef8c111e0c9a41843227cf2 by Oliver Kellogg.
Committed on 09/05/2021 at 15:47.
Pushed by okellogg into branch 'release/21.04'.
Fix crash reported in https://bugs.kde.org/show_bug.cgi?id=
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #21 from Oliver Kellogg ---
(In reply to Oliver Kellogg from comment #20)
> (In reply to milasudril from comment #18)
> > Any update on this task?
>
> A added support for C++11 "enum class" and it is working in a Qt4 based
> build.
> Howeve
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #20 from Oliver Kellogg ---
(In reply to milasudril from comment #18)
> Any update on this task?
A added support for C++11 "enum class" and it is working in a Qt4 based build.
However, on trying to import
https://invent.kde.org/sdk/umbrello
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #19 from Oliver Kellogg ---
Git commit 464c7132349e4cf10a84fc9e6f3792087a934158 by Oliver Kellogg.
Committed on 30/04/2021 at 19:11.
Pushed by okellogg into branch 'release/21.04'.
Support C++11 "enum class" in C++ Import:
lib/cppparser/as
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #18 from milasud...@gmail.com ---
Any update on this task?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=338649
Ralf Habacker changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #16 from Ralf Habacker ---
Git commit 13a513d629e86e8cc98d750f1d9e5741bbc8791a by Ralf Habacker.
Committed on 09/09/2016 at 05:34.
Pushed by habacker into branch 'master'.
Add c++11 code import test cases.
A +14 -0test/import/cxx/cx
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #15 from Ralf Habacker ---
Git commit d14553de1c33f9f087baa0d59d41223738eaa5d7 by Ralf Habacker.
Committed on 30/05/2016 at 21:30.
Pushed by habacker into branch 'master'.
Add missing license header.
M +19 -0unittests/TEST_llvm.cpp
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #14 from Ralf Habacker ---
Git commit 2de8b562409f8d502d0efe27c316e6ca4e2df1c8 by Ralf Habacker.
Committed on 28/05/2016 at 12:52.
Pushed by habacker into branch 'master'.
Add llvm test case.
M +19 -0unittests/CMakeLists.txt
A +29
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #13 from milasud...@gmail.com ---
Doxygen has an option for CLANG_ASSISTED_PARSING since version 1.8.4.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #12 from Ralf Habacker ---
(In reply to Patric Schmitz from comment #10)
> >> If this is a basic limitation to using clang, is this really the way the
> >> project should go?
>
> Probably the most reasonable way to go about it after all?
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #11 from Ralf Habacker ---
(In reply to Patric Schmitz from comment #10)
> >> If this is a basic limitation to using clang, is this really the way the
> >> project should go?
> >> Maybe it is possible to separate only the parser parts with
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #10 from Patric Schmitz ---
>> If this is a basic limitation to using clang, is this really the way the
>> project should go?
>> Maybe it is possible to separate only the parser parts without the whole
>> semantics and error checking from
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #9 from Ralf Habacker ---
(In reply to Patric Schmitz from comment #8)
> On 01/03/2016 01:01 AM, Ralf Habacker via KDE Bugzilla wrote:
> > ...clang, which needs to be called similar to a compiler
> > building the related source code
>
> I a
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #8 from Patric Schmitz ---
On 01/03/2016 01:01 AM, Ralf Habacker via KDE Bugzilla wrote:
> ...clang, which needs to be called similar to a compiler
> building the related source code
I actually see this as a major problem. Requiring people
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #7 from Ralf Habacker ---
(In reply to Ralf Habacker from comment #6)
> 3. The recently used parser is very tolerant against incomplete c++ code,
> which is not the case for clang, which needs to be called similar to a
> compiler building th
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #6 from Ralf Habacker ---
(In reply to milasudril from comment #5)
> I thought libclang would be usable. This way, new features would already be
> implemented there.
It may be usable, but noone has opened a working branch and tried to imple
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #5 from milasud...@gmail.com ---
I thought libclang would be usable. This way, new features would already be
implemented there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=338649
milasud...@gmail.com changed:
What|Removed |Added
CC||milasud...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=338649
Patric Schmitz changed:
What|Removed |Added
CC||bzk0...@aol.com
--- Comment #3 from Patric Sch
22 matches
Mail list logo
