[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] Recommendation for non-compliant PDE...
- From: "Niclas Hedhman" <niclas@xxxxxxxxxxx>
- Date: Fri, 15 Jun 2007 09:45:06 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=lkRZ3Zx+ZORgdTScdDLbBDiqFTC6C2ELfwk1YtnG/UjHJbUdzXFmQ+cD/9/yiHh4IQczqVL7p1bUIZj632tyFOdDunsZCuh21xuEXUPLU+o3hCnzQdSuJBH2CMQX8wi1YrM7mFKfbLEAZ3jGrdAkKIoLad6toUU8+cePGJZIA+s=
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
Any ideas of what one should do?
(Mind you this is not a problem in Equinox, only the PDE.)