Very unintuitive location of the assert toggle
Having the assert keyword toggle in the Path settings is bound to confuse a lot of people especially where it is placed, at the bottom of a very large page.
It would be better placed in the Compiler settings with the javac/jikes options. That is the intuitive place to put it IMHO.
Jacques
请先登录再写评论。
I think it should also be an intention for when you use assert wrong.
I completely agree - it's very easy to miss it stuck at the bottom of the Paths tab. However - I don't think it should be part of the compiler options. Enabling/Disabling assertions is done when running code, not compiling it (compare javac and java parameters, use -help).
How about including it in:
"Target JDK" section of the Paths/Library tab?; or
In the Run configuration?
Ah - ignore most of that (it's a bit early in the morning here). Confusing myself between enabling assertions on running code, and providing support for the keyword using the -source option...
So - remove the 'Enable assertions' option and replace it with a support for the -source option in the Compiler settings like you suggested? Then it would be easy to extend when using Tiger.