Becoming a contributor

[Milian Wolff]

On Wednesday, 29. September 2010 15:50:40 Aleix Pol wrote:
> I agree it's a good one. I was thinking about it once, I think the best for
> that one would be to process a regex all through the code for the TODO
> comments, that way you don't need to mess with AST's and well, comments
> usually are not there either so it's not something you would rely on.
> 
> So I would create a plugin that on project creation parsed all files using
> some simple regex to look for what the user wants and then whenever a file
> is saved it should be read again.
> 
> If you could get there I think that would be useful already and we could
> still do more on that later.

Sorry, but I object, and greatly so. Parsing huge projects is slow _already_ 
no need to slow it down even further by running regexps on each and every file 
in the project.

The correct way is to do the following:

- add a TODO severity to iproblem.h
- write a helper function that can be run on *single* comments (not on whole 
documents), best place would be 
kdevplatform/language/duchain/stringhelpers.cpp

Than use these tools in existing builders of the languages, e.g. in 
cpp/DeclarationBuilder::parseComments

Bye
-- 
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/20100929/f7979c1a/attachment.sig>