>"John Keiser" <[EMAIL PROTECTED]> writes:
>
>> The only plausible solution, then, that ports to javac is the use of
>> some sort of no-kiev comment style.
>
>Why bother with require/ensure equivalents for javac? If you use Kiev
>you win, if you use javac you lose. I don't see a big problem with
>that.
I think can't catch John's idea... Can you write me a three-line example?
Also, I do not think javac/guavac/etc needs analogs of require/ensure
You'll have checks in debug code, if compile with kiev, and you
do not have them if compile with others... I see no problems...
>I also don't particular like this whole "comment this and Kiev will
>understand it" and "comment this and Kiev will ignore it". It makes
>code ugly.
>
>Why not just use require/ensure in the normal Kiev manner and use sed
>to augment the source if Classpath is being compiled with a normal
>java compiler?
I'd recommend do not use sed scripts, since they may change
line limber infos... But if you can substitute require/ensure lines
with empty lines - I think it whould be better to not use /*{ ... }*/,
and use sed/awk/self-maiden tools, since this comment
really is not attractive ;-)
