Community
Participate
Working Groups
Build id: I20060620-1010 Type the following: public class X { /** @sin Press Ctrl-Space. I would expect @since to be proposed, and this is not the case. Note that: - when you press enter at the end of the first line, a closing bracket is inserted automagically (not shown here); - the 'sin' characters are presented in bold face, which augments the urge to press Ctrl-Space; - if you add a method or a field, code assist proposes @since. Also applies to other tags. The workaround exists and is obvious. Discussed a bit the subject with David. I admit that we cannot guess which tags are legal and which are not at this point (or simply dubious - I detected this using @deprecated, which is seldom used upon brand new members!). Yet, a programmer who has a clear view of what he is about to do should not be ampered by the tool. Here, the bold face tells him he can go with Ctrl-Space, and he gets no suggestion at all... in effect, while he believes typing @siCtrl-Space will save him time, he looses some. (In fact, the bold face is used after /** @, whichever letters you type, which is misleading by itself - but this bug specifically discusses the case of a legal prefix.)
There's 2 things here: 1) complete after /** @sin When comment is not ended, code is invalid and even scanner does not recognize any comment here (InvalidInputException). So, there's obviously no parse and no way to propose anything with current parse structure. I think that CompletionEngine here needs to be involved either to make proposals without using Javadoc parse or create a pseudo Javadoc node and parse it... 2) complete /** @sin<Ctrl+Space> */ without any declaration after. This point has been already raised: see bug 139621
Defer
Update summary as comment 1 problem 2) is now addressed...
Reopen as LATER is deprecated...
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
