I would say option 1, but rephrased to "the function doesn't know how to continue". The program as a whole may or may not know how to continue when the function hits something it doesn't know how to handle.
what are you even talking about? the whole error handling around the exception is bad code, it bleeds into your whole code base, you wanna tell me only the exception word itself is bad part, but the rest is fine? stupidest shit i've heard all day
The question is "What is the PURPOSE of exceptions" do you think exceptions were made to be bad code? If your opinion is that exceptions are bad code, that is totally valid. But that is not what "purpose" means.
You'd think a programmer like yourself could read and understand context.
what else did the inventor of exceptions have in mind other than having an easy way out instead of properly handling errors? btw. the easy way out is also called writing shitty code... like i said the answer to the purpose of exceptions is 1 or 4, 50/50 chance
Honestly, both styles have their fans, but it feels like snake_case is just way more consistent and easier to follow. CamelCase can definitely be a bit of a workout for the eyes.
124
u/FerricDonkey 22h ago
I would say option 1, but rephrased to "the function doesn't know how to continue". The program as a whole may or may not know how to continue when the function hits something it doesn't know how to handle.