評論
打印
And you actually urge them to shoot as many holes in it as possible,
同時，我們會要求客戶盡量找出其中的漏洞，
because you’d much rather know before you put in the feature than after.
因為我們喜歡在實現特性之前了解問題，而不是實現之后。
So unless a language feature is a complete slam dunk, we tend to make use of those kinds of sounding boards.
因此，除非一個語言特性是完全清晰的，否則我們都會使用諸如“發聲板”之類的辦法向用戶了解。
C# doesn’t have checked exceptions.
C#沒有受控異常。
How did you decide whether or not to put checked exceptions into C#?
你如何決定C#是否引入受控異常？
I see two big issues with checked exceptions: scalability and versionability.
我發現受控異常有兩個大問題：擴展性和版本控制。
I know you’ve written some about checked exceptions too, and you tend to agree with our line of thinking.
我知道你也寫了一些關于受控異常的資料，你應該會同意我的看法。
I used to think that checked exceptions were really great.
我過去真的認為受控異常是很好的想法。
Exactly. Frankly, they look really great up front, and there’s nothing wrong with the idea.
確實。坦率地說，最開始的時候，它們確實看上去很不錯，而且這種想法也沒什么問題。
I completely agree that checked exceptions are a wonderful feature.
我完全認同受控異常是很好的特性。
It’s just that particular implementations can be problematic.
只是某些特性的實現會有問題。
By implementing checked exceptions the way it’s done in Java, for example,
比如說，按照Java的方式，
I think you just take one set of problems and trade them for another set of problems.
你只是把一堆問題轉換成另外一堆問題。
In the end it’s not clear to me that you actually make life any easier. You just make it different.
最終，我并不認為你實際上已經把問題簡化了，你只是把這些問題換了個樣子而已。
Was there a lot of disagreement in the C# design team about checked exceptions?
C#設計團隊對受控異常有分歧嗎？
No, I think there was fairly broad agreement in our design group.
沒有，我們整個團隊達成 了廣泛共識。
C# is basically silent on the checked exceptions issue.
基本上，我們把受控異 常的問題暫時放置。
Once a better solution is known—and trust me we continue to think about it—we can go back and actually put something in place.
一旦找到更好的 解決方案,相信我，我們會繼續考慮它，我們會回過頭做實事。
I’m a strong believer that if you don’t have anything right to say, or anything that moves the art forward，
我堅信，如果沒有什么好說的，沒有更好的解決方案或路徑，
then you'd better just be completely silent and neutral, as opposed to trying to lay out a framework.
那么你最好完全保持沉默和中立，而不是去設計框架。
