基于调用特征的架构分类 [英] Categorizing architectures based on calling features

问题描述

调用函数有多种方式:调用栈、延续传递、消息传递和事件处理.您将这些功能的类别称为什么?召唤?按这些特性分类的架构叫什么?调用架构?

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?

推荐答案

您所要求的内容概括了调用约定的想法，因此您可能可以避免使用它从广义上讲.

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.

这篇关于基于调用特征的架构分类的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！