InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Call for Microsoft to Release Spec#

Posted by James Vastbinder on May 28, 2008

Sections
Development,
Architecture & Design
Topics
.NET ,
Language Design ,
Programming ,
.NET Framework
Tags
Spec#

Last month Greg Young, a Microsoft MVP and fellow InfoQ editor, initiated a grass roots effort asking for Microsoft to release Spec# as a whole or piece-wise in .NET.  In large font and asking for those with similar interests to leave a note, Greg declared his passion:

I want verifiable Software…

Spec# is an extension of the C# language and actually extends the C# type system to include non-null types and checked exceptions.  It also provides method contracts and object invariants. 

Greg posted a video he recorded of the actual altdotnet Spec# session presented by Mike Barnett and Rustan Leino.  If you listen closely you can hear the presenter ask for the community to let their voices be heard, around the 20 minute mark, if they would like Spec# to be folded into Visual Studio proper.

 Scott Hanselman also asked for community response when he released a Hanselminutes audio podcast of an interview he did with Mike Barnett and Rustan Leino.

Which would developers prefer: 

Spec# added to C# as a language extension?

or

Spec# added to .NET for multiple languages?

More resources needed by 陆 超 Posted
Re: More resources needed by John DeHope Posted
  1. Back to top

    More resources needed

    by 陆 超

    I'd like it intergrated into C# so that it has more attention, but considering the complicity of C# itself increasing every year, I think maybe it's better to make it a standalone product, But the most important thing is that microsoft should give it enough resource to evole anyway.

  2. Back to top

    Re: More resources needed

    by John DeHope

    I'd like them to normalize how the "?" syntax works. I want everything to be non-nullable by default. That means value types as well as reference types. If I want something, anything, to be nullable, I'll put a "?" on the type.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.