Post History
Bypassing source restrictions by storing data in the file name In some languages, like Pxem, programs are usually stored in the file name and the file's contents are irrelevant. On Somewhere Else,...
Answer
#2: Post edited
by
AndrewTheCodegolfer
·
2021-08-02T11:33:48Z (over 2 years ago)
- ## Bypassing source restrictions by storing data in the file name
- In some languages, like [Pxem](https://esolangs.org/wiki/Pxem), programs are usually stored in the file name and the file's contents are irrelevant. On Somewhere Else, a Pxem answer has been disqualified before because the file content did not adhere to restrictions even if the file name did.
Since this dynamic seems more than a little unfair, I propose that programs in restricted-source challenges should be:- normal programs where the file name doesn't matter and the file contents adhere to restrictions, or- empty/meaningless file content where the file name adheres to restrictionsThere might be some cases in which this won't work but I'll let the voters decide what's fair for this loophole and what isn't.
- ## Bypassing source restrictions by storing data in the file name
- In some languages, like [Pxem](https://esolangs.org/wiki/Pxem), programs are usually stored in the file name and the file's contents are irrelevant. On Somewhere Else, a Pxem answer has been disqualified before because the file content did not adhere to restrictions even if the file name did.
- I propose that the area where the source code is stored should adhere to restrictions. There might be some cases in which this won't work but I'll let the voters decide what's fair for this loophole and what isn't.
#1: Initial revision
by
AndrewTheCodegolfer
·
2021-07-25T11:32:39Z (almost 3 years ago)
## Bypassing source restrictions by storing data in the file name In some languages, like [Pxem](https://esolangs.org/wiki/Pxem), programs are usually stored in the file name and the file's contents are irrelevant. On Somewhere Else, a Pxem answer has been disqualified before because the file content did not adhere to restrictions even if the file name did. Since this dynamic seems more than a little unfair, I propose that programs in restricted-source challenges should be: - normal programs where the file name doesn't matter and the file contents adhere to restrictions, or - empty/meaningless file content where the file name adheres to restrictions There might be some cases in which this won't work but I'll let the voters decide what's fair for this loophole and what isn't.