PRE-PROPOSAL: Source and Encoding keyword (original) (raw)
Mark Mahieu markmahieu at googlemail.com
Sun Mar 15 18:23:11 PDT 2009
- Previous message: PRE-PROPOSAL: Source and Encoding keyword
- Next message: PRE-PROPOSAL: Source and Encoding keyword
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Buckley's slides on the modules JSR ( http://blogs.sun.com/abuckley/resource/Devoxx2008-ModularityInJava.pdf) show examples of specifying a required module version, including things like "java.core @ 1.7". Presumably things like java.lang and javax.lang.model will sit somewhere in this versioned module system, so wouldn't that be a more suitable way to approach this? I mean, why add yet another place to specify the version?
Mark
2009/3/16 Reinier Zwitserloot <reinier at zwitserloot.com>
As I've mentioned at least twice on coin-dev already, the JLS only needs to specify how the 'source' keyword sets the 'source' property of the CompilationUnit that contains the source keyword. As far as the JLS is concerned, this is a string value that has no further meaning. It's a bit like a comment in this sense. To be crystal clear: ** The JLS will NOT specify what is supposed to happen when you write "source 1.1;" in a JLSv3 view of the source file! **
- Previous message: PRE-PROPOSAL: Source and Encoding keyword
- Next message: PRE-PROPOSAL: Source and Encoding keyword
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]