Timeline for LOL'ing-Up Project Euler One
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
Apr 13, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
Jan 23, 2016 at 18:29 | history | bounty ended | Mathieu Guindon | ||
Jan 16, 2016 at 0:49 | comment | added | 200_success | This answer is the winner of Best of Code Review 2015 — Lots of Laughs category. Congratulations! | |
Jun 16, 2015 at 12:44 | comment | added | Nick Udell | For production source code, yes. For esoteric programming languages, no. The point is to be experimental, fun, or different with an esoteric language, and that does not necessarily mean it should be readable. Whitespace's readability is essentially zero, after all. | |
Jun 16, 2015 at 12:02 | comment | added | Vogel612 | @NickUdell the point of all source code is by definition readability.. Whether that's C, Java, Python, JS, ..., or yes, lolcode. | |
Jun 16, 2015 at 12:00 | comment | added | Nick Udell | Personally I disagree, as lolcats were typically all in SHOUTCASE. Sure, readability is better with lowercase variables, but that is not the point of lolcode. | |
Feb 4, 2015 at 2:03 | vote | accept | Mathieu Guindon | ||
Feb 2, 2015 at 16:27 | comment | added | Pimgd | It's like SQL in that aspect. | |
Feb 2, 2015 at 16:26 | comment | added | RubberDuck | Seriously agreed with this. All of the languages keywords are SHOUTCASE, variables should not be. | |
Feb 2, 2015 at 13:49 | history | edited | Vogel612 | CC BY-SA 3.0 |
added OR, properly indented code
|
Feb 2, 2015 at 0:29 | history | rollback | Vogel612 |
Rollback to Revision 1
|
|
Feb 2, 2015 at 0:24 | history | edited | Vogel612 | CC BY-SA 3.0 |
added 242 characters in body
|
Feb 2, 2015 at 0:06 | history | answered | Vogel612 | CC BY-SA 3.0 |