Spec# 是否足够稳定以使用? [英] Is Spec# stable enough to use?

问题描述

这里有人经常使用 Spec# 吗?在我开始在任何地方使用它之前，我想知道它是否足够稳定和强大.看起来语法正在影响 c# 4.0，这有望在 4.0 发布后更容易升级.想法?

Does anyone here use Spec# regularly? I would like to know if it is stable and powerful enough before I start using it everywhere. It looks like the syntax is influencing c# 4.0, which will hopefully make it easier to upgrade once 4.0 is released. Thoughts?

推荐答案

我想这取决于您所说的稳定"是什么意思.有两种可能的解释:

I guess it depends on what you mean by "stable". There are two possible interpretations:

1. 不会崩溃"
2. 不变"

我不知道#1，但如果你的意思是#2，那么，好吧，Spec# 已被废弃且不再开发，因此它可能与您将获得的一样稳定.

I don't know about #1, but if you mean #2, then, well, Spec# has been abandoned and is no longer being developed, so that's probably as stable as you're gonna get.

Spec#(称为 Boogie 和定理证明器/约束求解器 Z3) 现在是名为 .NET 的代码契约.成为一个库的结果是代码契约适用于任何 .NET 语言:C#、VB.NET、F#、Ruby、Python、JavaScript、Lisp、Smalltalk、Boo，你能想到的.缺点是你没有语言集成，所以没有很好的合同语法.

The techniques and tools that were used in Spec# (the static analysis tool called Boogie and the theorem prover / constraint solver Z3) are now part of a new library called Code Contracts for .NET. The upshot of being a library is that Code Contracts will work for any .NET language: C#, VB.NET, F#, Ruby, Python, JavaScript, Lisp, Smalltalk, Boo, you name it. The downside is that you get no language integration, so no nice syntax for contracts.

.NET 的代码契约将成为 .NET 4.0/Visual Studio 2010 的一部分，但遗憾的是，微软的任何语言都不会提供 DbC 支持.

Code Contracts for .NET will be part of .NET 4.0 / Visual Studio 2010, but unfortunately there will be no DbC support in any of Microsoft's languages.

这篇关于Spec# 是否足够稳定以使用?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！