It's a legitimate concern, but not necessarily a bug at this point. So it becomes a design decision: should Clojure support access to package-scoped fields?
Personally, my initial reaction is that it should not. Package-scoped fields are a quirk of Java. The solution on StackOverflow is adequate: write a small Java class with the correct package-level access. On the other hand, Clojure has a stated goal of seamless interoperability with Java. If you have use cases for which the lack of package-scoped field access is a serious problem, then I would encourage you to document them in a new page on the Clojure design wiki (dev.clojure.org). If you decide to do that, try to focus on the problems you're having and the inadequacy of existing solutions, rather than immediately proposing a change to the compiler. We've been using a process like this for feature discussions within the Clojure/core team. Although the process isn't very well documented or formalized yet, you can see lots of examples on the wiki, such as my recent efforts at http://dev.clojure.org/display/design/Asynchronous+Events -Stuart Sierra clojure.com -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
