Timeline for Default for Code Golf: Input/Output methods
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2014 at 9:47 | comment | added | John Dvorak | @MartinBüttner noted. I still don't like this option, but feel free to override my preferences. The vote split is very close to the threshold ATM. | |
| Nov 4, 2014 at 13:16 | comment | added | trichoplax is on Codidact now | The only time that I would object to a function taking input in the same way as a program is if the question was phrased "Write a function that takes the following arguments". This poll applies to questions that are not in such a specific format, so I see no reason to exclude functions that read from stdin. | |
| Nov 3, 2014 at 11:10 | comment | added | Martin Ender | @JanDvorak I don't see the relevance of good coding practices for code golf. And some languages don't even have functions and they aren't necessarily at a disadvantage by allowing functions. The idea of being more liberal in the options for I/O is so that each language can pick what's really shortest. | |
| Nov 3, 2014 at 6:43 | comment | added | John Dvorak | This violates the single-responsibility principle, the separation of concerns principle, and I don't think it's really useful in code golf. Moreover, functional programming languages won't let you do that at all, and I want some more love for Haskell. | |
| Nov 2, 2014 at 23:12 | history | answered | Martin Ender | CC BY-SA 3.0 |