A somewhat common pattern in source-layout is to have competitors write a program which does task A (usually cat or printing a constant), but when a transform B is applied to the program the modified program does B applied to A.
Here are a bunch of examples, (they also have very similar titles):
- Mirror quine (or my head hurts) [tag added] (and its duplicate I reverse the source code, you reverse the source code!) [tag added]
- Period 2 Reversed Quine
- I double the source, you double the output! [tag added]
- I shift the source code, you shift the input!
- I reverse the source code, you reverse the input!
- I transpose the source code, you transpose the input!
- Pass on your radiation
- I palindrome the source code, you palindrome the input!
- I (rev)?(pal)? the source code, you (rev)?(pal)? the input!
- I Rot-13 the source code, you Rot-19 the output!
Here are some marginal examples:
- The transform applied to the source and the output are similar but not the same:
- Fits the description by virtue of the fact that the source and the output are the same thing:
This seems like a good candidate for a tag:
- There are a number of similar challenges.
- They have been posted with some degree of regularity for an extended period of time (6 years since the first, the most recent was posted this week).
- There seems to be substantial room for novel challenges in the format.
- They are not easy to find using an existing combination of tags. (The titles are pretty formulaic, but hard to search and there is at least one example of a challenge in the group which does not use the format.)
- Is there a good reason not to make this tag?
- What should the criteria for this tag be? i.e. what should the tag wiki say?
- What is a good name for this tag?