Community
Participate
Working Groups
build 20040610 - 0800 - load SWT + UI from HEAD at 12 noon on June 10. - I have a single class in SWT called PrinterData that does not seem to compile. - the error is "Missing code implementation in the compiler PrinterData.java org.eclipse.swt/Eclipse SWT Printing/common/org/eclipse/swt/printing line 1 June 10, 2004 12:50:59 PM" - recompiling/delete and checkout again will not fix this. I'm not sure why this is happening
This is an older workspace (at least 1 week I think), not a new one.
strangely, when I change the constructor to the following: /** * Constructs an instance of this class with the given * printer driver and printer name. * * @param driver the printer driver for the printer * @param name the name of the printer * * @exception SWTError <ul> * <li>ERROR_NO_HANDLES - if there are no valid printers * </ul> * * @see #driver * @see #name */ public PrinterData(String driver2, String name2) { this.driver = driver2; this.name = name2; } it starts to compile.
Surely a side effect of bug 65180. I investigate...
Problem comes from following type of javadoc reference: public class Test { int field; /** * @see #field */ void foo(int field) { } } field is now incorrectly bound to parameter instead of field...
Created attachment 11900 [details] Patch to start lookup in more appropriate context I don't like the previous patch. I believe the problem is rather that you start the resolution in the context of the method, instead of the context of the enclosing type.
Actually, my patch does allow @param tags to resolve any longer. Need to make the JavadocFieldReference starts its lookup in parent scope alone.
Problem of this patch was that we would not allow to resolve @param tags parameter name reference... As the workaround is quite simple: rename parameters with different name than fields, we need to figure out if this is really necessary to fixed this for 3.0 or deferred it...
As this is breaking code in the visual editor, I think it is pretty serious.
Using: public class Test { int field; /** * Comment {@link #field} */ void foo(int field) { } } is causing the same problem. This is causing some grief during the build of the visual editor project.
In one of our classes we have several ctor's that have this type of syntax and resulted in compile errors and a broken build. Here's an example of one of the constructors: /** * Creates an empty instance with the given result index. * @param resultIndex the {@link #resultIndex}. */ public CompoundCommand(int resultIndex) { super(); this.resultIndex = resultIndex; commandList = new ArrayList(); } This code has been around for ages and has never been a problem until now.
*** Bug 66594 has been marked as a duplicate of this bug. ***
Must fix for 3.0. If we can get it finalized for RC2, we should contribute it. If not, then it will be for RC3.
Released for integration. Fix is stepping out of methodScope for implicit lookup only (using Scope#classScope()). Frederic - pls add regression tests.
Test cases added in JavadocTestMixed
Verified for 3.0RC2 I20040611