我认为一般情况下都要避免简写,因为这需要对一门语言更加精通,不是一般的多面手程序员所能掌握的。
I have found shorthand generally to be avoided, because it requires a deeper familiarity with a language than a generalist programmer would possess.
如清单12所示,这里可以使用简写形式,因为Retention只有一个成员变量。
As you can tell from Listing 12, you can use the shorthand form here, because Retention has a single-member variable.
因为不可能从清单5所示的简写形式中获益,所以您需要创建虽然稍微有点冗长,但是更容易理解的注释类型。
You don't get the benefit of the shorthand syntax shown in Listing 5, so you might as well be a little more verbose and create better self-documentation for your annotation type.
你可以叫她A,因为这个是她的简写名字。
因为语句(5)中的整个粗体表达式会出现在许多代码片段中,所以从这里往后我将它简写为TREAT ( …
Since the entire boldfaced expression in statement (5) appears in many code fragments, I will abbreviate it to TREAT ( … ) from now on.
因为语句(5)中的整个粗体表达式会出现在许多代码片段中,所以从这里往后我将它简写为TREAT ( …
Since the entire boldfaced expression in statement (5) appears in many code fragments, I will abbreviate it to TREAT ( … ) from now on.
应用推荐