Community
Participate
Working Groups
Defining a task tag starting with "//" may lead to an "Unexpected end of comment" error if the respective source file ends with a "/* */" comment where the second slash is the very last character in the source file. ----- Code snipped ------ public class Sample { public Sample() {} } /* * CVS log information: * $Log$ */[EOF] --- End of snippend ------ P.S.: The error also occurs in 2.1.0.
Task tags should be identifiers. This being said, we shouldn't crash if bogus tags are given to us.
Fixed. Accept now '//' as task tag. [jdt-core-internal] Changes done in checkTasktag(int,int) method Scanner. Note that now lookup for tags in comment start at first character (and not second one as before) to be able to detect starting double '/'. Changes duplicated in PublicScanner. 2 test cases added in NegativeTests
It doesn't fail anymore, but: //toto is seen as a task if //toto is a task tag. It could simply be the starts of a line comment.
Verified in 200405180816