这样表达式认为在时间以前测试并且明显配齐。
Such expressions are thought to be tested by time and therefore evidently true.
在这个例子里，两个模式的唯一区别就是这个守卫表达式，但是这样足够编译器来区分它们了。
In this example, the only difference between the two patterns is the guard expression, but that's enough for the compiler to differentiate them.
这样你们就有一个很简单的表达式。
但是，这里经常有人提问这样一个问题：如何编写查询表达式才能从任何复杂的DOM中获取正确的节点？
It is here, though, that a common question is asked: How do you write the query expression to get the correct node from an arbitrarily complex DOM?
这样一来，使用其中任何一种语言的遵从表达式都可以顺利地迁移到该字段支持的另一种语言。
Compliant expressions in either language then facilitate the smooth migration to the other language which may also be supported by the field.
这会导致其他操作数也被转换成64位的类型，这样在对表达式进行赋值时就不需要再进行转换了。
This will cause the other operands to be promoted to 64-bits and no further conversion is needed when the expression is assigned.
将表达式转换为sql，这样他们就能被服务器执行了(这是linq到sql所做的工作)。
Convert expressions into SQL so that they can be executed by a server (this is what LINQ to SQL does).
除此以外，它还支持在配置中使用表达式，这样就能实现与动态构建的URL之间的连通了。
Moreover, it supports the usage of expressions in its configuration, which enables connectivity with dynamically built URLs.
这样可能使表达式变得很复杂。
这样您就不必每次都要重新键入正则表达式。
This saves you the trouble of having to re-type the regular expression every time.
可以通过在CAM模板规则中指定printmessage表达式来处理这样的场景。
Such scenarios can be handled by specifying a printmessage expression in the CAM template rules.
一个JET中这样的例子是：通过扩展该扩展点，在XPath表达式中使用camelcase(参见jet源代码中的CamelCaseFunction)。
An example of this is in JET's ability to use camelcase in XPath expressions by extending this extension point (see the CamelCaseFunction in the JET source code).
XPath 2.0的量化表达式可以明确说明如何执行这样的比较。
The quantified expressions of XPath 2.0 let you explicitly state how you prefer to perform such comparisons.
如果不喜欢使用这么长的字符串连接语句，另一种方法是使用字符串格式操作符，可以使用下面这样的表达式。
If you prefer not to use a long string concatenation statement like this, an alternative is to use the string formatting operator which enables you to have an expression like.
可以利用address/street/text()或者 /person[last-name="Gosling"]/address[@type="work"]/city这样的XPath表达式来得到街道名。
You can get the street with an XPath expression like address/street/text() or maybe /person[last-name="Gosling"]/address[@type="work"]/city .
另外一种解决方案是对整个表达式进行转换，这样就可以在赋值时进行符号扩展。
Another solution is to cast the entire expression such that sign extension occurs on assignment. For example, consider the problem caused by the following.
不过，我们还是先看看表达式求值的经典算法，这样您就会明白W 3eval方法的差异究竟有多少。
First, however, we'll look at the classical algorithms for evaluating expressions, so you can see how W3Eval's approach differs.
清单1定义了这样一个XPath表达式。
我将模板匹配从 /修改为Invoice，这样就不需要在每个XPath表达式的开头部分重复根元素名称。
I've changed the match on the template from / to Invoice so that I don't have to repeat this root element name at the start of each XPath expression.
清单3中的实例修改了AgeValidation_def规则定义表达式，这样就可以使用trim函数。
The example in Listing 3 modifies the expression of the AgeValidation_def rule definition so that it makes use of the trim function.
只要知道文档有什么元素以及在什么位置，$rss->channel->item->title这样的表达式很方便。
Expressions such as $rss->channel->item->title are great as long as you know exactly which elements are in the document and exactly where they are.
而MathML是针对Web环境设计的，在这样的环境下，表达式显示在未知的且可能动态更改大小的窗口中。
However, MathML is designed for a Web context where the expression is being displayed on a window of unknown and potentially dynamically changing size.
如果支持BC特性，可以设置version 1.0让它在表达式求值的元素中生效，这样就不用担心类型匹配问题了。
If the BC feature is available, you can set version 1.0 to be in effect for an element with expression evaluation, eliminating worry about type mismatches.
如果只需要对一部分节点进行序列化，那么在检查所有节点之前使用精确的XPath表达式限制条件，这样效果会好很多。
If only a subset of nodes needs to be serialized, it is much better to limit with precise XPath expressions up front than to inspect all the nodes later.
与在单个dbspace中保存多个表或索引片段提高了查询性能，这样做胜过将每个分段表达式存储在不同的dbspace中。
Storing multiple table or index fragments in a single dbspace improves query performance over storing each fragmented expression in a different dbspace.
Encryptor要理解XPath表达式，这样才能识别出需要加密的xml元素。
Encryptor understands XPath expressions in order to identify the XML element for encryption.
为了访问ApplicationProxy 关系的属性，您可以使用像 ${current.application.name} 这样的表达式。
To access attributes of relations of ApplicationProxy, use expressions like ${current.application.name}.
为了访问ApplicationProxy 关系的属性，您可以使用像 ${current.application.name} 这样的表达式。
To access attributes of relations of ApplicationProxy, use expressions like ${current.application.name}.
应用推荐