Timeline for A way not to forget to check for errors in C
Current License: CC BY-SA 4.0
26 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2019 at 21:38 | comment | added | Deduplicator |
Generally, one uses the return-value to determine whether an error occurred, though errno is sometimes needed for disambiguation. It is only cleared if (potentially) needed for disambiguation or manually, and set if an error occurred.
|
|
| May 7, 2019 at 21:10 | comment | added | Blrfl | Don't try to bend a language that's essentially a chainsaw without a blade guard into something suitable for use by the undisciplined. The answer you selected is spot on. | |
| May 7, 2019 at 20:24 | comment | added | David Lehnsherr | Yes, it would be. I want to have approach “you can’t hide errors” like Go programmers have. But it seems like it’s really much easier to write usual C code or choose another programming language. | |
| May 7, 2019 at 20:04 | comment | added | Blrfl | Wouldn't good code review be easier? | |
| May 7, 2019 at 19:55 | comment | added | David Lehnsherr | Ok, changed my question. Now I believe it’s concrete. Thanks. | |
| May 7, 2019 at 19:54 | history | edited | David Lehnsherr | CC BY-SA 4.0 |
deleted 19 characters in body
|
| May 7, 2019 at 19:47 | vote | accept | David Lehnsherr | ||
| May 7, 2019 at 19:43 | comment | added | candied_orange | @DaveMarshall I believe Andreas F. is trying to get you to edit your current question before it gets closed and deleted. | |
| May 7, 2019 at 18:34 | answer | added | Christophe | timeline score: 11 | |
| May 7, 2019 at 17:55 | history | edited | David Lehnsherr | CC BY-SA 4.0 |
added 36 characters in body
|
| May 7, 2019 at 17:08 | comment | added | David Lehnsherr | Thank you, Andreas. Sure, I’ll make my next questions specific. | |
| May 7, 2019 at 16:54 | answer | added | Sazzad Hissain Khan | timeline score: 1 | |
| May 7, 2019 at 16:50 | review | Close votes | |||
| May 14, 2019 at 3:05 | |||||
| May 7, 2019 at 16:35 | comment | added | Andres F. |
Welcome, Dave. In order to be on-topic here, you should frame this in the form of a concrete question with ideally a single "best" answer that can be accepted. This should be a hint that in its current form this is probably off-topic here: "Any critics, advices?". Chatty, open-ended questions are off-topic here (regardless of whether they are good or bad!)
|
|
| May 7, 2019 at 16:26 | history | edited | David Lehnsherr | CC BY-SA 4.0 |
edited body
|
| May 7, 2019 at 16:20 | history | edited | David Lehnsherr | CC BY-SA 4.0 |
added 51 characters in body
|
| May 7, 2019 at 16:15 | comment | added | David Lehnsherr | I want to code in pure C, @mrflash818 | |
| May 7, 2019 at 16:14 | comment | added | David Lehnsherr |
Standard library functions (malloc(3), fopen(3), access(3), stat(3), etc) set errno to indicate errors. The scope is global, @candied_orange
|
|
| May 7, 2019 at 16:10 | comment | added | candied_orange | What exactly is the scope of errno? I can see it being reset and tested but it's never set in this story. The code and the text seem to be telling me different stories. | |
| May 7, 2019 at 16:08 | comment | added | David Lehnsherr | I will force it only in my projects. | |
| May 7, 2019 at 16:06 | comment | added | mrflash818 | Wrap your C code in C++, and throw Exceptions for error conditions, or just code as pure C++ with the throwing of Exceptions for error conditions. | |
| May 7, 2019 at 16:05 | history | edited | David Lehnsherr | CC BY-SA 4.0 |
added 102 characters in body
|
| May 7, 2019 at 16:05 | comment | added | Robert Harvey | Ok. How do you plan on enforcing the use of the replacement functions? Who watches the watchers? | |
| May 7, 2019 at 16:00 | history | edited | David Lehnsherr | CC BY-SA 4.0 |
added 102 characters in body
|
| May 7, 2019 at 15:55 | review | First posts | |||
| May 7, 2019 at 20:53 | |||||
| May 7, 2019 at 15:50 | history | asked | David Lehnsherr | CC BY-SA 4.0 |