Timeline for get_line(): An alternative implementation of standard C library's getline() function
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2022 at 9:00 | history | tweeted | twitter.com/StackCodeReview/status/1501845315095183361 | ||
| Mar 6, 2022 at 6:23 | history | edited | user245050 | CC BY-SA 4.0 |
added 81 characters in body
|
| Feb 27, 2022 at 7:48 | history | edited | 200_success |
edited tags; edited tags
|
|
| Feb 27, 2022 at 6:07 | history | edited | user245050 | CC BY-SA 4.0 |
added 18 characters in body
|
| Feb 25, 2022 at 15:33 | history | edited | user245050 |
edited tags
|
|
| Feb 25, 2022 at 12:44 | history | edited | Toby Speight |
edited tags
|
|
| Feb 24, 2022 at 17:48 | comment | added | Richard Neumann |
normally lines are not greater than 256 bytes. -- [citation needed]
|
|
| Feb 24, 2022 at 16:49 | comment | added | user245050 | I have worked for Cisco Systems and Juniper Networks. | |
| Feb 24, 2022 at 16:13 | comment | added | Toby Speight | @Amit, you clearly work in a different software company than I do. My development team do care about correctness (that's normally proven by the unit tests), but they also care that the code is maintainable. Good style helps a team to keep code correct when it has to be updated due to new requirements. | |
| Feb 24, 2022 at 16:11 | answer | added | Toby Speight | timeline score: 4 | |
| Feb 24, 2022 at 15:58 | comment | added | user245050 | The code review that happens in a software company is more about bugs, wrong logic, performance improvements, optimizations, etc. rather than programming style. Out here, on codereview.stackexchange.com, it is the opposite - almost all focus is on programming style rather than bugs, wrong logic, etc. | |
| Feb 24, 2022 at 14:41 | comment | added | Mark Bluemel | Well done on encouraging people to review your code, mate! | |
| Feb 24, 2022 at 14:34 | comment | added | user245050 |
I have also not seen anyone giving positive reviews like I have reviewed your code and it all looks good. In this case, people skip giving reviews. People here are only interested in giving negative code reviews.
|
|
| Feb 24, 2022 at 14:28 | comment | added | user245050 | What I have found out is that people here review programming styles rather than reviewing for bugs, wrong logic, major performance improvements, etc. | |
| Feb 24, 2022 at 14:25 | history | edited | user245050 | CC BY-SA 4.0 |
deleted 16 characters in body
|
| Feb 24, 2022 at 14:07 | comment | added | Toby Speight | If you're really using K&R style, you should also be using old-style function definitions instead of prototypes - why so inconsistent? | |
| Feb 24, 2022 at 11:16 | history | asked | user245050 | CC BY-SA 4.0 |