Timeline for Shortest code for Seven-Eleven
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2016 at 15:09 | history | edited | Paul R | CC BY-SA 3.0 |
Add language tag for syntax highlighting
|
| Jul 12, 2011 at 18:35 | comment | added | user unknown | b can run to 711/3, c to 711/2. (a,b,c) can then be precomputed (see my scala-solution). By optimising for speed, one would let b run to (711-a)/3, c to (711-a-b)/2 but not for golfing. | |
| Jun 19, 2011 at 7:43 | comment | added | Paul R | @Peter: good point - I may have to work on this | |
| Jun 19, 2011 at 6:25 | comment | added | Peter Olson | If you feel dirty doing that sort of thing, then you will have some critical limitations in code golf. | |
| Jun 18, 2011 at 7:59 | comment | added | Paul R | @Joey: thanks, I could do that but I think I'd feel dirty afterwards. ;-) | |
| Jun 17, 2011 at 22:10 | comment | added | Joey Adams |
You can make it shorter by abusing implicitly-declared arguments, rather than explicitly declaring variables: main(a,b,c,d){ instead of int main(void){int a,b,c,d;
|
|
| Jun 17, 2011 at 21:34 | history | answered | Paul R | CC BY-SA 3.0 |