Patch: TODO highlighting in comments

[Sven Brauch]

It'd also be very useful for developing. :)
And yeah, for switching git branches for example, reparsing everything would
be cool too.

2010/11/8 Esben Mose Hansen <kde at mosehansen.dk>

> On Sunday 07 November 2010 00:32:36 Nicolas Alvarez wrote:
> > I have only used that action when trying to track down bugs in the C
> > ++ parser, where doing a full re-parse gave different duchain than
> > incremental parsing while typing.
> >
> > I can't think of why an end-user would need this action.
>
> Well, I can. Here is a couple:
>
>  * After upgrading libaries (if you're on debian unstable, that is a weekly
> occurance)
>  * After running some external script or tool
>  * After the parser getting it's internals corrupted (again) so that it
> will
> actually find all uses.
>
> Of course, this could be automated, but until it is a "reparse everything"
> is
> a very good idea. It is also a confidence thing: Once we get no reports
> that
> reparsing everything fixed something, we know we are catching all cases.
>
> How to reparse everything is also, btw, a quite common question I get.
>
> --
> kind regards, Esben
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101108/55244958/attachment.html>