Timeline for Print a random maze
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2011 at 21:01 | comment | added | Alexandru | Please let me know how you think the question can be improved. | |
| Jan 31, 2011 at 19:34 | history | edited | Mike Bethany | CC BY-SA 2.5 |
Placate author of poorly worded question
|
| Jan 31, 2011 at 19:26 | comment | added | Mike Bethany |
Then the other languages have to include the code it takes to call them or include #!/usr/bin/env python, for example, in their code. As I said I'll write a real solution too, this was just pointing out the poor quality of the question itself (and many others) and demonstrates we need to have better guidelines. And finally pointing to a question does not make the answer to the question the actual rules for the site. But fine, here's your new version...
|
|
| Jan 31, 2011 at 16:40 | comment | added | Alexandru | Cannot edit. I meant 'incomplete' not 'cheating'. I like the idea of the maze. | |
| Jan 31, 2011 at 16:34 | comment | added | Alexandru | Not really as long as it specified in the question. See meta.codegolf.stackexchange.com/questions/13/… . Moreover, unlike JavaScript Ruby supports argument reading and writing to standard output. Your solution is cheating compared to others who solved the problem the right way. | |
| Jan 31, 2011 at 16:04 | comment | added | Mike Bethany | Actually it doesn't say anything about stdout (that's also not a reasonable stipulation because someone might be using a language that doesn't print to stdout) and it's commonly accepted that inputs are to a function/method. To the person down voting this, it solves the problem as specified so don't hate the mazer hate the maze. | |
| Jan 31, 2011 at 12:24 | comment | added | Alexandru | Good, but make sure it respects the protocol (height and width from command line, maze printed to stdout). | |
| Jan 31, 2011 at 3:08 | history | answered | Mike Bethany | CC BY-SA 2.5 |