News for hackers. Stuff that matters.

A comment on Phrase origin: Why do we "call" functions?. Parent comment

Re:Phrase origin: Why do we "call" functions? by antod on Wednesday July 09, 2025 @12:55AM (#44506448)
I'm guessing "throw" came about after someone decided to "catch" errors.

As for "raise", maybe exceptions should've been called objections.

[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by zahlman on Wednesday July 09, 2025 @12:08PM (#44511745) 

  RuntimeObjection: autopsy report changed contents during cross-examination
[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by maxbond on Wednesday July 09, 2025 @09:36PM (#44516384)
"Exception" comes from hardware/state machines, and the name reflects that they may not be error cases. For instance, if an embedded device is waiting for a button press, then pressing that button will put the MCU into an exceptional/special state (eg interrupting execution or waking up from sleep).

But surely those days are in the past. We should call them objections, because they're always used for errors and never for control flow. [1] After all, that would be an unconditional jump, and we've already settled that those are harmful.

[1] https://docs.python.org/3/library/exceptions.html#StopIterat...

[ Parent | on HN ]