调用的

When we call SubmitChanges at the end it will transactionally update all of the product prices.

在最后调用SubmitChange方法是，它就会自动地通过调用事务对所有的产品的价格进行更新。

But it's all for naught because no amount of infrastructure can ever hide those problems of distribution.

RPC的根本问题是，它尝试让一个分布式的调用看起来像本地调用一样。

All the dynamic invokes we have seen are rather slow if we wanted to invoke repeatedly the same method.

所有动态调用，我们看到的是相当缓慢，如果我们想重复调用同样的方法。

And -- are perfectly safe to use in single-threaded servers, because even if the client app is multi-threaded and makes method calls from different threads, the COM library serializes method calls into our server.

从不同的线程++和-是十分安全使用单线程服务器，因为即使客户端应用程序是多线程，并使方法调用，COM库序列化为我们的服务器方法调用。

Do you see how it unwinds and goes down the layers until at the very bottom, it has the call that you would have originally had to make if this feature did not exist yet?

您看出它是如何展开并逐步调用低层直到按钮组件了吗，还有它执行的那些如果该特性不存在时本该由您执行的调用？

Whetting Your Appetite If you ever wrote a large shell script, you probably know this feeling: you'd love to add yet another feature, but it's already so slow, and so big, and so complicated; or the feature involves a system call or other function that is only accessible from C ..

如果你写过大规模的 Shell 脚本，应该会有过这样的体会：你还非常想再加一些别的功能进去，但它已经太大、太慢、太复杂了；或者这个功能需要调用一个系统函数，或者它只适合通过 C 来调用。。。

You only have to change interrupts to API calls and it's done.

你仅需要的是把DOS中的中断调用变成API调用。

If the random number is equal or less than the chance, it loads the spell from the weapon that hiddedthe targed, load the spell id, if it is indeed a OnHitChance-like event, it will cast the spell.

如果随机数小于或等于这个机率，程序会调用隐藏在武器上的技能攻击目标，但需要一个OnHitChance这样的事件才能调用

Not only will the constructor be called at unforeseen times, it might also be called for prefabs or inactive game objects.

在任意的时候不光可以调用构造函数，还可能会调用预设或未被唤醒的游戏物体。

To correctly handle slot disconnections during calls (e.g., when the dereference operator is invoked), one must construct the iterator to skip over disconnected slots.

为了正确处理在调用中的插槽断开（例如当调用解引用运算符时），你必须让迭代器跳过已断开的插槽。

We have no common name for a mime of Sophron or Xenarchus and a Socratic Conversation; and we should still be without one even if the imitation in the two instances were in trimeters or elegiacs or some other kind of verse--though it is the way with people to tack on 'poet' to the name of a metre, and talk of elegiac-poets and epic-poets, thinking that they call them poets not by reason of the imitative nature of their work, but indiscriminately by reason of the metre they write in.

索夫农 、森那库斯和苏格拉底式的对话采用的模仿没有一个公共的名称；三音步诗、挽歌体或其他类型的诗的模仿也没有——人们把&诗人&这一名词和格律名称结合到一起，称之为挽歌体诗人或者史诗诗人，他们被称为诗人，似乎只是因为遵守格律写作，而非他们作品的模仿本质。

The relationship between communicative competence and grammar teaching should be that of the ends and the means.

交际能力和语法的关系应该是目标与途径的关系。