I'm happy to do that in the future if there's a consensus about this on meta, but currently that's not how we roll. ;) (Also if we bring this up on meta we should address reusing file names at the same time.)
Is it difficult to type "flags count" into the search box? We could compile every single post about what counts and what doesn't and make a directory type post that links to all of the other posts. Seems like a lot of effort.
@Rainbolt I've approved that but it seems specific to encodings, not flags in general.
Maybe that blurb should be replaced with "you can use any encoding that you didn't make up" and a separate paragraph summarising the rules for compiler flags.
I will change to "It is accepted practice to count non-standard compiler flags or any other non-standard marks required to get the interpreter/compiler to do what you need it to do as part of the score."
yeah, but then the bit about encoding is gone entirely (which I think is important). hence the suggestion to just put the compiler flag stuff into its own paragraph, and change the encoding bit to say that the encoding must have existed before the challenge (just as the language)
Identifying a Sonnet
This challenge is about determining if a given file (read-in from stdin) meets the criteria to be a sonnet. You may use any language for this challenge.
Definition of a Sonnet
Has 14 Lines (lines are denoted as the standard newline on your operating system).
Has a definit...
So far, submissions consisting of multiple files have simply been counted by summing up the scores of the individual files. Also file names aren't counted as long as they are arbitrary. (We do count file names if the code depends on them to work correctly.)
I've been making (ab?)use of that in R...
well that's fair enough I guess... but you don't really get more than one character's worth by splitting the files, do you? and most of the time you can actually get the flags for a single byte, since most interpreters that have interesting flags also have -e
@Rainbolt can you invoke your code as lang -e "code"? then lang -eb "code" is one byte. can you not invoke your code like that, but do you have to call it as lang file? then lang -b file is 3 bytes.
@Optimizer because convenience... you'd probably use an unprintable character as the delimiter which you don't use otherwise
it doesn't really add anything and just makes things more annoying for everyone involved
@Martin So again, the three character per flag is total nonsense, and the real rule is you add x characters to your score where x is the number of additional characters you had to type. x could be three, but it could also a hundred other things. Three has nothing to do with it.
@Rainbolt yeah, the tag wiki would not have read "flags count 3 bytes" ;)
@Optimizer yay for consistency.
I really don't understand why you're so keen using the same (pretty random) approach for a completely different problem. it's apples and oranges anyway...
@MartinBüttner I don't like the way you presented it
First, you disconnect yourself from the answer. I wholly back mine. Second, you state "this is not an issue". It's not clear what you are talking about there.
"This is not an issue" either means that there is no question worth answering here, or the answer to the question is no because the abuse is not an issue
Identifying a Sonnet
This challenge is about determining if a given file (read-in from stdin) meets the criteria to be a sonnet. You may use any language for this challenge.
Definition of a Sonnet
Has 14 Lines (lines are denoted as the standard newline on your operating system).
Has a definit...
