Hello,
First of all, I have been practicing very regularly for almost a year now, sometimes for whole days… Sometimes for whole nights;)
I understand better the memory management, the philosophy, I read a lot on the subject, I see the extent of the ZIG compiler, frankly, I am impressed by the team as well as their work,
My question :
what I haven’t quite figured out yet is how or why and to what extent, should we write try unrechables etc. and is that implied.
Throw like that there is a lot to say
a) In a closed software, I mean who uses functions of which we are sure, should we put the hypothetical error management in place.
Even if there is a possibility of data inconsistency, but managed upstream.
put tries everywhere ??? with in !void etc…
b)
Writing functions which are normally generated (the code) by the project, but which can be coded manually, providing for error handling is understandable to me, but to what extent,
- the compilation error, there, I don’t care,
- the error due to the inconsistency of data which implies the non-functioning of the program?? if I dare to say that you define a window in there that she, you cannot write is a nonsense; even if the window is displayed; ???
- why am I asking his questions, when you provide the user with functions and you type a string of try or catch unreachable; etc
- I’m not talking about real error handling, but theoretical error assumptions;
writing this, I have part of my answer, but I would like to have another point of view
There are error handling videos and links that explain how to handle, but no philosophy of why and how and how far to go and what not to go.