| IWorkinCopy should extend ICompilationUnit, and not the opposite [message #8337] |
Tue, 29 April 2003 06:40 |
Eclipse User |
|
|
|
Historically, the JavaModel defined ICompilationUnit and IWorkingCopy; but
we believe they are incorrectly related to each other (ICompilationUnit
extends IWorkingCopy). We would like to take advantage of the 3.0 release so
as to reorganize our API and make it more coherent.
Compilation units denote file units, and working copies are providing an
in-memory abstraction of a unit being edited. A working copy can be created
from a compilation unit; its contents can be changed independently from the
underlying unit, as long as the working copy contents isn't committed.
A working copy thus adds functionalities to a compilation unit, and working
copy services are defined by IWorkingCopy. However, ICompilationUnit is
currently extending the IWorkingCopy interface, though it should be the
other way around. We believe that client code will read better, and will
provide some insights on how to migrate existing code.
If you disagree with this evolution, please let us know, and annotate bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36987 accordingly.
|
|
|
Powered by
FUDForum. Page generated in 0.25715 seconds
Home