3 ms·
I think “raise” comes from the fact that the exception propagates “upward” through the call stack, delegating the handling of it to the next level “up.” “Throw”
by flufluflufluffy 1y ago
I think “raise” comes from the fact that the exception propagates “upward” through the call stack, delegating the handling of it to the next level “up.” “Throw” may have to do with the idea of not knowing what to do/how to handle an error case, so you just throw it away (or throw your hands up in frustration xD). Totally just guessing
- owlbite 1y agoI suspect it comes from raising flags/signals (literally as one might run a flag up a flag pole?) to indicates CPU conditions, and then that terminology getting propagated from hw to sw.
- comex 1y agoI would have thought it came from the concept of 'raising an issue' or even 'raising a stink'.
- Findecanor 1y agoSounds plausuble. Some of the earliest exception handling systems did not have any semantic difference between CPU exceptions and software exceptions.
- devnullbrain 1y agoYou can still use SIGUSR1 and SIGUSR2 for it.
- deleted 1y ago[deleted]
- reverendsteveii 1y agoidk because there are some circles in which boolean variables are called flags but I've never seen them referred to as being raised or unraised/lowered, only set and unset
- kps 1y ago… which could come from raising the voltage of a signal indicating a condition.