Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Comments on Default Rules: Loopholes

Parent

Default Rules: Loopholes

+9
−0

What sort of loopholes are assumed to be disallowed in any challenge on this site?

One loophole per answer, please. Vote up answers if you want them disallowed, and down otherwise.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+4
−1

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, 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.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

2 comment threads

I disagree (2 comments)
general (1 comment)
I disagree
Lundin‭ wrote over 2 years ago

If there is to be such a rule, it needs to be more specific. In C and C++ you have various tricks such as the #line directive which can be used to trick the program into thinking the file name is something else - might be handy in some scenarios. There's also the argv/argc command line parameters where argc[0] is the name of the executable, but also a writeable location that could be exploited to save explicit variable declarations.

Lundin‭ wrote over 2 years ago

Examples like the above seem like valid clever tricks that should be encouraged rather than forbidden.