Timeline for Scanning a directory and listing contents in an HTML file
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Jan 21, 2016 at 17:24 | comment | added | chillworld | @EricStein Seems like mine standard is not the same as your standard coding, witch is fine. There are many standards, your way, mine way and even other ways. It's not wrong to know how you can improve code and certainly not wrong to code it like that. | |
| Jan 21, 2016 at 15:14 | comment | added | Eric Stein | It makes the code non-standard, adds an extra line, and consumes a tiny bit of extra memory. Taking a 1% runtime savings isn't worth it to me unless there's a demonstrated performance issue and that 1% makes a significant difference. | |
| Jan 21, 2016 at 14:32 | comment | added | chillworld | @EricStein If you make yourself the habit of doing this, you don't have to do premature optimization, it's your first code what works already slightly faster. We help people to improve there knowledge so they can create better code from the first time. | |
| Jan 21, 2016 at 14:05 | comment | added | Eric Stein | I think a 1% savings that makes the code less standard is premature optimization. | |
| Jan 21, 2016 at 7:03 | history | edited | chillworld | CC BY-SA 3.0 |
added 1 character in body
|
| Jan 21, 2016 at 6:59 | comment | added | Sky | Thank you for the good advice, especially for the last point :) | |
| Jan 21, 2016 at 6:54 | history | answered | chillworld | CC BY-SA 3.0 |