Valid use of goto for error management in C?

by

FWIF, I find the error handling idiom you gave in the question’s example to be more readable and easier to understand than any of the alternatives given in the answers so far. While goto is a bad idea in general, it can be useful for error handling when done in a simple and uniform manner. In this situation, even though it’s a goto, it’s being used in well-defined and more or less structured manner.

More Related Contents:

  1. I got an unknown error on my coding for a C program [closed]
  2. Error handling in C code
  3. Scanf won’t execute for second time
  4. How can I catch a 404?
  5. Can I rely on malloc returning NULL?
  6. Should I check if malloc() was successful?
  7. c99 goto past initialization
  8. Why GCC compiled C program needs .eh_frame section?
  9. When implementing an infinite loop, is there a difference in using while(1) vs for(;;) vs goto (in C)?
  10. How a stream error indicator affects following input code?
  11. Is it possible to store the address of a label in a variable and use goto to jump to it?
  12. How to "LoadLibrary" in C? [closed]
  13. Comparing a pointer with integer
  14. Why do I get a segmentation fault with strcmp [closed]
  15. What’s the best way to check if a file exists in C?
  16. Unit Testing C Code [closed]
  17. Why does integer division by -1 (negative one) result in FPE?
  18. How does “while(*s++ = *t++)” copy a string?
  19. What is “:-!!” in C code?
  20. How to detect UTF-8 in plain C?
  21. Drawing a character in VGA memory with GNU C inline assembly
  22. How big can a malloc be in C?
  23. zero length arrays [duplicate]
  24. How to compile an MPI included c program using cmake
  25. Pthread Run a thread right after it’s creation
  26. Initializing a struct to 0
  27. Where are syscalls located in glibc source
  28. how to use yy_scan_string in lex
  29. Is ‘long unsigned’ as valid as ‘unsigned long’ in C?
  30. Integer overflow in C: standards and compilers

Leave a Comment