EJB 3.0异常处理(EJB 3.0 exceptions handling)

 
 
 这是什么其他用例， 
 
 
 简洁（因此，只要你习惯了它，因为毕竟它根本不会牺牲可读性！） - 任何时候你需要检查一些东西，或者如果它是真的，就使用它，或者是其他值是错误的（这是为了 - 为 - or反转它 - 而且我非常故意避免实际的关键字 - 或者像True和False ，因为我在谈论每个对象，而不仅仅是bool ！）。 
 
 任何计算机屏幕上的垂直空间都是有限的，并且在给出选择的情况下，最好花费在有用的可读性辅助工具上（文档集，评论，策略性地将空行分开块） 
 
inverses = [x and 1.0/x for x in values]
 
 成六个如： 
 
inverses = []
for x in values:
    if x:
        inverses.append(1.0/x)
    else:
        inverses.append(x)
 
 或更狭窄的版本。 
 
 
 
 和/或这个相当不直观的实施的基本原理是什么？ 
 
 
 由于一些语言（如标准Pascal）没有详细说明评估顺序和and和or的短路性质，所以初学者通常不会被“不直观”所绊住。 Turbo Pascal和语言标准之间的差异之一是Turbo当时最流行的Pascal方言，它正是Turbo实现的and并且很像Python以后（以及C语言早期的版本.. ）。 

 
 
What are other use cases of this,
 
 
Conciseness (and therefore clarity, as soon as you get used to it, since after all it does not sacrifice readability at all!-) any time you need to check something and either use that something if it's true, or another value if that something is false (that's for and -- reverse it for or -- and I'm very deliberately avoiding the actual keywords-or-the-like True and False, since I'm talking about every object, not just bool!-).
 
Vertical space on any computer screen is limited, and, given the choice, it's best spent on useful readability aids (docstrings, comments, strategically placed empty lines to separate blocks, ...) than in turning, say, a line such as:
 
inverses = [x and 1.0/x for x in values]
 
into six such as:
 
inverses = []
for x in values:
    if x:
        inverses.append(1.0/x)
    else:
        inverses.append(x)
 
or more cramped versions thereof.
 
 
 
and/or what is the rationale for this rather unintuitive implementation?
 
 
Far from being "unintuitive", beginners regularly were tripped up by the fact that some languages (like standard Pascal) did not specify the order of evaluation and the short-circuiting nature of and and or; one of the differences between Turbo Pascal and the language standard, which back in the day made Turbo the most popular Pascal dialect of all times, was exactly that Turbo implemented and and or much like Python did later (and the C language did earlier...).