Community
Participate
Working Groups
I like to set up "todo" tags. But I don't always remember how I enter them. Because task tags are sensitive to case, I have to define todo, TODO, ToDo, Todo, and so on in order to see them all. Seems to me that task tags shouldn't care about case.
Java is a case-sensitive language, so I would not change this. Same for javadocs. May reconsider at later stage.
I'd like to add a little to this one. Yes, it is true that Java is case-sensitive, but the contents of comments are not. You are just doing some extra processing on the contents of comments you recognize with a keyword, and so you are free to choose how case sensitive to be. Our group has standardized on the use of "todo" and "future" tags. Some of us tend to use TODO and some tend to use todo. In order to see all the todo items, you have to define at least 4 task names: TODO, todo, Todo, ToDo, and maybe even tOdo, tODo, tODO, tOdO, and such for those that are mistyped. It's silly to require that.
Using the same argument, you could argue that @SEE should work as @see, but it doesn't.
I disagree. JavaDoc is a defined standard within the realm of Java, with Java's case sensitivity. But task tags are an artifact of Eclipse, not defined within Java or JavaDoc. We know they are different because /** @see other */ is recognized, whereas // @see other or /* @see other */ are not recognized. However, all of these get recognized by Eclipse: /** todo Fix me */ /* TODO Fix me */ // Todo Fix me This is really a team programming issue. I can remember to do my tags in lowercase, but I cannot count on my team members to do so. Some of them have had a habit of using upper or mixed case in their todo items over the years (some of the code is quite old now). We are on a kick to ensure we are warning free, and that all the todo's are done or removed. And so I want to see them all, regardless of case. I cannot think of any harm that would coming in recognize a task tag in a case-insensitive fashion. And I really think you'd be helping development teams find ALL their task items.
I understand your argument, though I want to minimze the amount of time spent checking comments (for this matter Javadoc tags and TODO fall into the same category from my end).
Fair enough. You might be doing more than you think. Instead of one todo tag and one future tag, my group members have to define about four todo tags and three future tags to catch just the most common variations of these tags. So in my group, you're scanning for 7 tags in a case-sensitive fashion rather than just 2 tags in a case-insensitive fashion. Just something to think about...
Reopening
Adding option to make task check case insensitive. Default is still case sensitive. Added regression test NegativeTest#test411
Fixed
UI is missing (see bug 55929) but verified that the JDT Core functionality is in build I200403240800.
