---------- Forwarded message ---------- From: Thomas Watson <[EMAIL PROTECTED]> Date: Jun 15, 2007 3:06 PM Subject: Re: [equinox-dev] Recommendation for non-compliant PDE... To: Equinox development mailing list <[EMAIL PROTECTED]>
Hi, I added your message to the bug JDT bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=122915. This is really a JDT compiler bug. In Eclipse many have worked around this bug by having the exported classes implement *every* method which is inherited from an internal class it is extending. For example, public void foo() { super.foo(); } Unfortunately that would not work if the method foo is final in the internal class and I agree it is not ideal, but it is a work around. Tom. *"Niclas Hedhman" <[EMAIL PROTECTED]>* Sent by: [EMAIL PROTECTED] 06/15/2007 02:45 AM Please respond to Equinox development mailing list <[EMAIL PROTECTED]> To "Equinox development mailing list" <[EMAIL PROTECTED]> cc Subject [equinox-dev] Recommendation for non-compliant PDE... Hi, The PDE bug that disallow exported subclasses to extend from non-exported internal classes is getting on my nerve. The internal superclass is something I insist of not exporting, since it is something we don't want to support, and users are demanding that we do so because otherwise their code doesn't compile in PDE. What does the Equinox community recommend? Do the wrong thing and export the internal classes as a compile-time work-around, or what? I don't use Eclipse, and don't have a problem myself, and it annoys the crap out of me to give into these kinds of demands, when the tooling is crappy... Any ideas of what one should do? (Mind you this is not a problem in Equinox, only the PDE.) Cheers Niclas
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
