Well, there's still module-info.java but the syntax of the contents of this file aren't actually java. It looks java-ish, with brackets and semicolons and such, but it's not java, not in the slightest. The 'module' keyword remains in limbo (it would be a 5th access level; less public than 'public', with 'public' serving as the signal that this is in fact reachable from outside the entire module, and 'module' being what public is now), that's tightly wound up with java the language, at least more or less. Nobody is stopping scala etc from adding something for this.
jigsaw module files are a from-the-ground-up redesign of jar files. They are now opaque (no longer 'zip files', i.e. oracle is free to change whatever they want), and class files will or might become legacy concepts, as they aren't the speediest choice these days. If javac emitted files in a different fashion, booting up a large java app would be significantly faster. This part in particular has all sorts of backwards issues with it, but presumably all those old APIs (such as java agents which get to change class files, ClassLoader.defineClass, etc) will continue to be supposed, with the speedier new format shortcut taken only if none of these features end up being used. On Thursday, March 22, 2012 5:33:45 PM UTC+1, Simon Ochsenreither wrote: > > Hi Reinier, > > has something happened in regard to some criticized requirements like > having class files somewhere which some dynamic languages where unhappy > about? Earlier versions where also quite mixed up with Java-the-legacy. Has > this been fixed? > > Bye, > > Simon > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/zD7COjVnMKAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
