PROPOSAL: Compiletime information access (original) (raw)
Vilya Harvey vilya.harvey at gmail.com
Tue Mar 24 16:12:56 PDT 2009
- Previous message: PROPOSAL: Compiletime information access
- Next message: PROPOSAL: Compiletime information access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2009/3/24 <rssh at gradsoft.com.ua>
> evaluating during compilation?) and security (what security model does it > operate under?). >
Security model of java compiler. We already have al this potential problems with annotations processing, where any java code can be auto-discovered and run. And practice shows that this is not the biggest problem of language.
Good point, I forgot about the annotation processor.
The difference is that use of annotations is syntactically distinct from regular Java code, whereas the Compiletime class in your examples is not. I think this could lead to confusion, but maybe that's just me.
Possibility to write unmaintainable code exists.
But if think in such way, than creation of turing-complete programming language was fatal security error ;)
I like it! :-)
Vil.
- Previous message: PROPOSAL: Compiletime information access
- Next message: PROPOSAL: Compiletime information access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]