Timeline for Macro for allocation in C
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 13, 2019 at 21:54 | comment | added | Norbert Incze | Your opinion is totally understandable, the function is simple, the code is not safety critical or anything like that. But I still recommend to use describing names and try to improve, refactor each part of your code whenever you can. You will improve by practicing it on these little functions. After months it helps a lot, even at these functions, when you look at their names and you totally understand what it is doing. I do not even mention when others have to look at your code. Remember, we read code way more times than it was wrote/refactored. | |
| May 13, 2019 at 21:38 | comment | added | klutt | Describing names are good, but for such a simple function as this I'd say it's abundantly clear. And I would like to use a function instead, but for my purpose, it is not possible. Besides, the link you gave does not illustrate an issue that could arise in this code. | |
| Feb 4, 2019 at 14:38 | comment | added | Norbert Incze | @jpa explained it quite well, so I did not went into details, but I focused on mentioning different, possible error sources. | |
| Feb 4, 2019 at 12:48 | comment | added | Toby Speight | "because of security reasons" is very vague, and arguably untrue. It's certainly not enough to justify an obvious pessimisation. | |
| Feb 2, 2019 at 17:55 | review | First posts | |||
| Feb 2, 2019 at 18:40 | |||||
| Feb 2, 2019 at 17:53 | history | answered | Norbert Incze | CC BY-SA 4.0 |