Feb-08-2021, 06:55 PM
my function that works on the file system should inform the caller what error it encounters and where. the where would just be the path in a str. i am pondering the best way to tell the caller what the error is. the obvious is to let the error raise an exception. but not all errors would normally do so such as discovering something not being the way that is wanted, such as a file having 600 bytes when wanting one with 512 bytes. the function and why it is called has a different kind of abstraction. i want the caller to be able to figure this out quickly. is it considered OK to return an int code number or a word in a str that can be tested by the caller?
i'm also thinking that i should just make up my own exceptions but i have never done that and don't know how involved that is.
i'm also thinking that i should just make up my own exceptions but i have never done that and don't know how involved that is.
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.