然而,在主循环中,您使用了一个条件分支。
一个组合碎片用来把一套消息组合在一起,在一个序列图中显示条件分支。
A combined fragment is used to group sets of messages together to show conditional flow in a sequence diagram.
这些细微差别可以在工作流中用简单的条件分支(“如果帐户是新的,则…”)处理。
The trivial differences could be handled with simple conditional branches (" if account is new, then... ") in the workflow.
当进行条件分支、向函数传递值、从函数返回值以及其他操作时,首选槽内的值才是关键的。
When doing conditional branching, passing values to functions, returning a value from a function, and several other scenarios, the value in the preferred slot is the one that matters.
流程的WS - BPEL表示形式(请参见图2)与业务模型类似,因为存在连接在一起的步骤以及条件分支逻辑。
The WS-BPEL representation of the process (Figure 2), is similar to the business model in that there are steps which are wired together, along with conditional branching logic.
这种形态不包括常规形态中常见的循环、条件和分支。
This form does not include the loops, conditions, or branches found in the generic form.
实现决策分支条件。
为分支输出构建条件。
您可以通过许多方法来测量代码覆盖率:通过评估代码行或语句的覆盖面、条件覆盖面、分支覆盖面等等。
You can measure code coverage in several ways: by assessing line or statement coverage, condition coverage, branch coverage, and so on.
修改与分支和链接相关联的条件。
预先计算CASE条件和IFTHENELSE条件,并立即跳至适当的分支。
Pre-compute CASE condition and IF THEN ELSE conditions and jump into the right branch right away.
如果跳转请求跨过这些分支,则可能会违反这些条件,并可能会导致意外的行为和异常。
If a jump request crosses these branches, these conditions may be violated and this may result in unexpected behavior and exceptions.
决策元素对输入业务项中的条件进行评估,然后根据评估结果选择是执行 Yes分支还是No分支。
The decision element evaluates the condition from the input business item and, based on the evaluation result, it branches to either the Yes or No branch.
您可以定义这些decision的输出条件,以便捕获详细信息,了解这些值是如何判定项目应流入的分支的。
You define output conditions for these decisions to capture in detail how these values determine the branch the item flows into.
条件寄存器(ConditionRegister,CR)是反映特定操作结果并提供测试(及分支)机制的32位寄存器。
The Condition register (CR) is a 32-bit register that reflects the result of certain operations and provides a mechanism for testing (and branching).
ClosureStylesheets让我们可以使用@if、@elseif和@else,从而基于某些变量的值来创建条件语句的分支。
Closure Stylesheets allows the use of @if, @elseif and @else in creating conditional branches based on the value of some variables.
但是,在不用分支的情况下,有条件地设置这些位比较困难。
However, it is a little more difficult to set these bits conditionally without branching. The assembly language version looks like this.
报告分支覆盖的工具试图度量决策点(比如包含逻辑AND或OR的条件块)的覆盖率。
Tools that report branch coverage attempt to measure the coverage of decision points, such as conditional blocks containing logical ANDs or ORs.
清单11被视为一个庞大的条件语句,它基于请求url中的o参数的值执行一个特定的分支。
Listing 11 is best thought of as a giant conditional statement, which executes a particular branch based on the value of the o parameter in the request url.
流程的输入和输出条件与它可能的执行分支之间的错误匹配,可能会成为错误的来源。
A possible source of errors is the mismatch between the input and output criteria of the process and its possible execution branches.
这两个分支相互区别的原因并不明显,除非建模人员希望分隔decision条件,这在使用流程监视的应用程序中可能会有此要求。
It's not clear why they were distinguished from each other unless the modeler intended to separate the decision conditions, which might be required in an application that USES process monitoring.
需要特别说明的是,如果活动充当了隐式的merge,则它们的输入条件必须与可选分支精确匹配。
In particular, the input criteria of activities that act as implicit merges must exactly match the alternative branches.
假设有一个具有互斥分支的循环流;每个分支都有一些应用于该分支中所有活动的前置条件和不变量。
Consider a cyclic flow that has mutually exclusive branches; each branch has preconditions and invariants that apply to all activities in the branch.
成功和失败条件与循环、条件和分支一样,都是这种图的组成部分。
Both success and failure conditions are part of this type of diagram, as are loops, conditions, and branches.
Task4有一个输入条件,只需将业务项A和B 提供给上面的分支,而它针对下面分支的则是一个单独的条件,其中包含业务项 A、B 和D。
Task 4 has an input criterion requiring only business items A and B for the upper branch, while for the lower branch it has a separate criterion that includes business items A, B, and D.
例如,如果一个条件标上了“likely”,那么编译器可以把代码的True部分直接放在分支指令后面(这样就不需要执行分支指令)。
For example, if the conditional is marked "likely" then the compiler can place the True portion of the code immediately following the branch (which will not be taken).
在开发人员使用有条件代码时,常常知道最可能执行哪个分支,而哪个分支很少执行。
When working with conditional code, you often know which branch is most likely and which is not.
管理员现在可以为活动的传出链接提供转换条件值,以迫使流程沿着所选的分支运行。
Administrators can now provide transition condition values for outgoing links of an activity, to force the process down the chosen branch.
因此,为了避免出现分支,我将尽可能多的有条件工作分载到SPE中。
Therefore, to avoid branches I offload as much of the conditional work onto the SPE as possible.
所以原人格理论说,相同人格,足以使之成为相同的人,新版人格理论添加了一个无竞争者条件,添加了一个无分支条件。
So where the original personality theory said, same personality, that's good enough for being the same person, the new version throws in a no-competitors clause, throws in a no branching clause.
应用推荐