Comments on: Legacy-Proof Your Frameworks

By: Eric Burke

Eric Burke — Fri, 14 Dec 2007 00:13:15 +0000

Damn I wish they used something other than < for generics… { would have been so much more HTML friendly.

By: Dan

Dan — Thu, 13 Dec 2007 23:28:01 +0000

I guess I need to escape it too

I’m talking about the

By: Dan

Dan — Thu, 13 Dec 2007 23:26:54 +0000

Eric, you need to escape the in your example code. Opera treats it as an unclosed tag and everything else afterwards looks a bit mental. I had to use Safari to post this comment.

By: Alex Miler

Alex Miler — Wed, 12 Dec 2007 16:36:56 +0000

Great post, Eric. The Eclipse guidelines put everything that is implementation in a *.internal.* package. You can actually use Eclipse (and OSGi) to enforce the visibility constraints on these packages as well, although often people don't bother to set this up. And of course, that kind of visibility issue is exactly what JSR 294 superpackages are intended to address. You can define a component in terms of a superpackage and only publicly expose certain packages. Use of classes from other packages in the superpackage should fail to compile.