[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse-dev] Re: [platform-ui-dev] Platform UI'splug-ins converted to manifest format
|
I'm coming it a little late here, but it seems to me that
part of the beauty of the "public internal" packages is that you basically put
the onus on folks who use it. It's highly discouraged, but maybe between eclipse
releases another plugin writer really needs to access internal classes in
someone else' s plugin. In a later release those internals may be moved to the
api layer, but at the time, there was no choice.
The PropertySheetEntry sorting request I logged a while
back is such a case -- to sort the sheets I needed to recreate the
PropertySheeyEntry class in its entirety, and I believe it referenced internal
classes. Now that the update is in (applied template method pattern with a few
"protected" hooks), that one's not needed, but it serves as a good
example.
I really like the new compiler warning that can watch for
access restrictions based on naming, so I'd think that would be sufficient,
along with the ever-present stern warning. (Assuming that wasn't an April Fool's
bit -- I haven't tried it yet ;) )
Of course I may have misread the issue while skimming
through this thread. If so, feel free to bonk me...
Later,
-- Scott
