Hi Jan, I've got a specific use-case I'd like your feedback on:
* My library exports an enum. * Users must be able to pass enum values into exported API methods. * The enum contains a method to ensure that each possible value defines a different implementation. * The method is only meant to be invoked by non-exported implementation classes; however, seeing as those classes reside in other packages the method is public. So I'm left with a public method that I don't want users to be able to invoke. Ideally I don't want them to see the method either, but I don't think there is much I can do about that. Does this represent a legitimate case for public, non-exported methods? Or is there a better design that would meet the requirements? Thank you, Gili -- Sent from: http://jigsaw-dev.1059479.n5.nabble.com/
