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 owlbite on Wednesday July 09, 2025 @01:32AM (#44506618)
I 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.
[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by Findecanor on Wednesday July 09, 2025 @02:35AM (#44506923)
Sounds plausuble. Some of the earliest exception handling systems did not have any semantic difference between CPU exceptions and software exceptions.
[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by devnullbrain on Wednesday July 09, 2025 @10:59AM (#44510825)
You can still use SIGUSR1 and SIGUSR2 for it.
[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by comex on Wednesday July 09, 2025 @01:47AM (#44506683)
I would have thought it came from the concept of 'raising an issue' or even 'raising a stink'.
[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by reverendsteveii on Wednesday July 09, 2025 @01:18PM (#44512594)
idk 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
[ Parent | on HN ]
Re:Phrase origin: Why do we "call" functions? by kps on Thursday July 10, 2025 @02:26PM (#44524014)
… which could come from raising the voltage of a signal indicating a condition.
[ Parent | on HN ]