Loophole for other challenge

Question

You are to post an answer you posted that exploited a loophole in the challengers question. Bonus points if it caused them to rewrite the question.

For example, one challenge was to write a program that such that if a random character is removed, it still works, and your score is how many characters it fails on. Some one posted the empty program, since then it would fail on no characters (though the compiler would fail) and the question had to be changed. He was unrightly down-voted, so I hope he sees this challenge.

This is a popularity contest, so whoever gets the most votes wins!

Answer 1

In my answer to Loophole for other challenge, I deliberately exploit the fact that the poster didn't specify that the answer had to be responding to another question. This made my answer recursive and self-referential.

I also golfed my answer (even though it was a popularity contest). 0 bytes of code.

Answer 2

Render a version of the BBC Micro owl logo

I used curl to grab the challenge page and outputted an answer posted by someone else.

Answer 3

In Weirdest way to produce a stack overflow, i submitted an answer that opened a web browser and displayed stackoverflow.com.

Answer 4

In Shortest Program to Sort a List of numbers into Odd and Even Category, the question clearly states:

... The Size of the program is the size of the body of the function, i.e. excluding the size of the function signature.

I thought, "Why such a bizarre and specific rule?" And as I was trying to golf down my initial submission, it dawned on me--default parameter values! According to the language spec, they're definitively not part of the function body, so I went ahead and submitted my final solution: a function whose body is a single character. That must have been what the OP wanted!... right?...

Needless to say, it did not win. :/

After accepting another answer, the challenger did eventually add a footnote as to why the one-character solution wasn't considered. The rules of the challenge, however, still remain unchanged (as of the time of this post). So, in the strictest interpretation of the rules, who would you say actually won? ;]

Answer 5

In Write a hash function for Morse Code, the OP didn't specifically exclude negative or floating point values which are entirely usable as hashes. Using this loophole, I was able to get a better than "perfect" score of 236. There was much griping, but the OP never changed the question, despite promising to, and the loophole was subsequently exploited by almost every other poster!

Answer 6

In the question https://codegolf.stackexchange.com/questions/21391/output-with-1-on-stdout-using-a-0-byte-source-code, it states that it will give a bonus of -500 bytes if we output '1' to the console using a source-code file which is 0 bytes long.

My answer is this one and 'abuses' the null devices in windows and linux.

The question wasn't rewritten, but this answer gave me a pretty big hole to go to the gold (the -500 byte bonus). Why? Because the null devices have ALWAYS 0 bytes in size and are guaranteed to exist!

Answer 7

Quoting this question:

Your goal is to add two input numbers without using any of the following math operators: +,-,*,/.

Additionally, you can't use any built-in functions that are designed to replace those math operators.

I posted this answer, it was not very popular though. Quoting from my answer:

And, as suggested by @Ismael Miguel (althought he was not exactly suggesting this), by really abusing the rules underspecification, we can note that only +, -, * and / operators were forbidden, but += was not, so it is allowed (it is not a built-in function either, since it is not even a function). This way, we can express the instruction with just 4 characters (and it will always work with negatives and non-integers too for both values):

y+=x

Answer 8

In the same question that @Victor refered (Add without addition (or any of the 4 basic arithmetic operators)), i gave this asnwer.

Basicly it "ABUSES" the Javascript internal casting to integer of the boolean values.

---

And This question itself exploits a loophole: there is NOTHING saying we can't refer to the same question in the answers. Or the number of answers. Or the number of answers from the same question.