根据调用功能对架构进行分类
调用函数有不同的方式：调用堆栈、连续传递、消息传递和事件处理。您如何称呼这些功能的类别？祈求？您将这些特征分类的架构称为什么？调用架构？
子问题：除了给定的四个之外，此类功能还有哪些示例？
There are different ways of calling functions: call stacks, continuation passing, messaging and event handling. What do you call the category of these features? Invocation? What do you call architectures categorized by these features? Invocation architecture?
Sub question: Other than the four given, what are some examples of this type of feature?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您所要求的内容概括了调用约定的想法，因此您可能能够在扩展的意义上使用它。
“函数调用风格”和“调用风格”也可能有效。
What you're asking for sort of generalizes the idea of calling conventions, so you might be able to get away with using that in an expanded sense.
"Function calling style" and "calling style" may also work.
“调用函数的方式”对我来说似乎很合适。为什么要费尽心思让事情变得比现在更困难呢？
如果您正在撰写的论文非常频繁使用这个短语，您可以通过在顶部定义“调用架构”的含义来节省一些文字。我不知道有任何术语用于此目的。
"Ways of calling functions" seems appropriate to me. Why go out of your way to make things more difficult than they already are?
If you're writing a paper that is using this phrase very frequently, you might save a few words by defining what you mean by "Invocation Architecture" at the top. I'm not aware of any term used for this.