@Geobits we've been discussing Underwater a bit (chat.stackexchange.com/rooms/16028/… if you're interested)... it looks like a few of the hazards have to be modified. I think I've fixed nets and jellyfish, but there is still a slight possibility that shrimp aren't enough of a threat.
"The player starts in a random room on an icosahedral map (thus there are 20 rooms in total, connected to each other like the faces of an icosahedron, and every room has exactly three exits)."
wtf, that would be such an easy game of hunt the wumpus
figuring out the room map is the bulk of the difficulty in that game
@Geobits cheers... I'll be updating the KotH tag wiki with some common practices, and I'll link to your challenge as an example for persistent pipes if you don't mind
In computing, a named pipe (also known as a FIFO for its behavior) is an extension to the traditional pipe concept on Unix and Unix-like systems, and is one of the methods of inter-process communication (IPC). The concept is also found in OS/2 and Microsoft Windows, although the semantics differ substantially. A traditional pipe is "unnamed" because it exists anonymously and persists only for as long as the process is running. A named pipe is system-persistent and exists beyond the life of the process and can be deleted once it is no longer being used. Processes generally attach to the named pipes...
basically just redirecting STDIN and STDOUT from another process to yours
I appear to have resolved the space-complexity problem (solver using 14MB instead of in excess of 2GB) but it's still slow as something slow, having already clocked 9 minutes on the 4-way multiplexer
This site (http://programmingpraxis.com) publishes every week very interesting code challenges, that could totally fit here.
Example: http://programmingpraxis.com/2014/07/25/number-words/ : that would be a perfect code-golf question.
Do you think we could, or should automatically publish those ...
Myself and some friends used to have competitions and we'd always network them, because I'd use C#, one of them would use Python, and another would use Bash, and the server would be C++ because it's the only thing we can agree on
would it make sense to assemble a reliable interface for each language, so people can quickly put together networked challenges?
@Sparr, Someone will have to write a wrapper for non java submissions I'm afraid, I don't know how to do that. And thanks for looking at the starting positions.
am I correctly reading that player 1 starts on the north edge of the floor, flying south, and player 2 starts on the south edge of the ceiling, flying north?