Patch: TODO highlighting in comments

[Milian Wolff]

On Saturday 13 November 2010 22:50:31 David Nolden wrote:
> 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.
> > 
> > Never.
> > 
> > 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...

Then what is it?
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101114/b668e022/attachment.sig>