Patch: TODO highlighting in comments
zwabel at googlemail.com
Sat Nov 13 21:50:31 UTC 2010
2010/11/13 Milian Wolff <mail at milianw.de>:
> On Saturday 13 November 2010 20:40:59 David Nolden wrote:
>> Btw. we could also put TODO's into the code-model, and then show them
>> in the class-browser. The class-browser has all the required
>> technology ready and working, efficiently. It would maybe just need
>> some additional filtering option. Then we could limit the
>> problem-reporter to the currently open file.
> If someone looks for classes, he has the class browser.
> If someone looks for problems in his code, he looks at the problem tool view.
> These are totally different use cases and should not mix just because they
> happen to share some backend code. You can create a shared lib and reuse the
> code in both plugins, but don't push unrelated functionality into plugins.
A TODO is not a parsing problem, it's a part of your code. It doesn't
belong into the "Problem Reporter" too much either. Anyway...
More information about the KDevelop-devel