Default Rules: Flags and Other Compile-Time Options
How should we deal with flags / command line options when scoring entries?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I say we follow the established rules on SE:
Rather than dealing with inconsistent schemes for adding flags, let's just consider each separate invocation of a compiler/interpreter/whatever a separate implementation (and thus a separate language by our rules).
E.g. Scala -language:postfixOps counts as a different language from vanilla Scala, and we don't care about counting how many bytes the flags are.
0 comment threads
IF flags take arguments, those arguments count for the code length
For example, in Japt, -F"string" is a flag that prints "string" if the output is falsy - in my opinion this should add 6 bytes on to the length of the answer (in language Japt -F).
0 comment threads