On Sunday, March 17, 2013 6:02:07 AM UTC+1, vemv wrote: > Ahhh I tracked it down - the class was not public. I thought .java files > had to define at least (and at most) *one* public class/enum/interface. > > How much sense can it make to define a private class in its own file? :( >
It makes perfect sense: complecting access control with file organization is not exactly a plus for a language. The existing restriction of one public class per file is nuisance enough. Many times it forces the unwieldiness of nested classes upon you. -Marko -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
