Re: Source Scanner...
"Trond Norbye" <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.tasklist.devel |
|---|---|
| Message-ID | <[email protected]> |
Tor Norbye said: >> >> 1. It creates tasks for "tags" that do not reside in a comment block. > > The tasklist is not java specific. Thus, you can add TODO markers in > your XML files, in your .txt files, in your .html files. I am aware of that, but ... (see below) > > The list is generated by matching a regular expression (which > the user can customize, which defaults to > > DefaultScanRegexp=\\bTODO\\b|\\bFIXME\\b|@todo\\b|\\bPENDING\\b|\\bXXX\\b > ## Additional candidates: HACK, WORKAROUND, REMOVE, OLD > > (See Global Options to customize it) > > If we add in specialized behavior like "ignore matches outside > java comments" it complicates the user model I think. > One could do one of the following: a) Let the user select a source-scanner engine to use on a given file type the same way that the user may select the indention engine to use. b) Let the user select something like: Ignore matches outside comments in known filetypes and list the filetypes. c) Let the user specify the start/end tokens for a block comment, start token for an "end-of-line" comment for given file types (and let the user specify the extensions as regexs (java/c/c++ user similar comment style). > > Well, it's not as unusual as you think. The problem is that often the > tag does not appear at the beginning of the line. I myself write code > such as this: > hashMap = new HashMap(maxSize*2); // Decent factor? XXX > If you strip out the stuff on the left of the token you're left > with very little. Interesting ;) I "oversimplyfied" things again ;) (but I guess that I still could do some kind of "washing" of the line) > > Well, if you insist we could make it optional. But NetBeans already has > too many options. We're not quite emacs yet though :) > I don't insist, but I would really appreciate it since I spend a lot of time in front of the computer... (and now it "irritates" me to look at the comments in the tasks, and "non-comment" tasks) To avoid too much settings we could test for a "undocumented" property, so you can toggle it on/off and watch the result when I'm done.... Trond