Bug 34002

Description Eric Nickell 2003-03-06 13:36:29 EST

If one has a second top-level class in a compilation unit, and another class in
the package makes a reference to it, the Java editor says that it cannot resolve
the type name, although the Package Explorer indicates that it compiles cleanly.

I find it quite unnerving to have red ticks next to my scroll bar for legal code.

I'm running I20030227/linux/gtk on a dual-processor 2GHz pentium.

Here is a test case (in two compilation units):

/*
 * Created on Mar 6, 2003 by Eric Nickell.
 * 
 * Copyright (C) 2003, Palo Alto Research Center, Incorporated. All rights reserved.
 */
package buildI20030227.editorcantseeclass;

/**
 * @author nickell
 */
public class FirstClass {

}

class SecondClass {
}


/*
 * Created on Mar 6, 2003 by Eric Nickell.
 * 
 * Copyright (C) 2003, Palo Alto Research Center, Incorporated. All rights reserved.
 */
package buildI20030227.editorcantseeclass;

/**
 * @author nickell
 */
public class ThirdClass {
	SecondClass thisReferenceToSecondClassIsFlaggedAsErrorByEditorButIsReallyLegal;
}