为什么信号不仅仅称为事件？-Whyaren'tsignalssimplycalledevents?

Actually, "signals" have been around longer than events have. In the earliest usage, a signal was an asynchronous way for processes to get notified that events had occurred. Since Unix is much older than Django (and since a lot of the Django work came from pydispatcher, where the original stuff was done), the name has stuck.

实际上,“信号”比事件更长。在最早的使用中,信号是进程通知已发生事件的异步方式。由于Unix比Django年龄大得多(并且由于很多Django工作来自pydispatcher,原始的东西已经完成),因此名称已经停滞不前。

Events are really signals, you might say!

你可能会说,事件真的是信号!

Signals typically have an association with an operating system facility and events are typically application-defined. In some technology stacks, the OS-level stuff may be hidden well enough that there isn't a difference in the API, but in others perhaps not.

信号通常与操作系统设施相关联,并且事件通常是应用程序定义的。在某些技术堆栈中,操作系统级别的内容可能会被很好地隐藏,以至于API中没有差异,但在其他技术中可能没有。

Afaik Qt had the first signal/slot implementation. Qt's docs explain the metaphor: "A signal is emitted when a particular event occurs". The distinction is so subtle that the nomenclature has been blurred.

Afaik Qt有第一个信号/插槽实现。 Qt的文档解释了这个比喻:“当特定事件发生时会发出信号”。区别是如此微妙,以至于命名法已经模糊不清。

You might as well ask "Why aren't events simply called signals?". Differences in terminology happen.

您不妨问“为什么事件不仅仅被称为信号?”。术语的差异发生了。