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.

Iterators for VB

Posted by Jonathan Allen on Aug 14, 2008

Sections
Development,
Architecture & Design
Topics
Programming ,
.NET
Tags
Visual Basic.NET ,
Functional Programming

Visual Basic's Paul Vick recently revealed a proposal to add iterators in a yet unnamed version. While meant to address the same use cases as C#'s yield return statement, the proposal looks more like something out of a function programmer's playbook.

C#'s iterator is a form of continuation, a rarely used technique popular in languages such as Scheme. Looking at the source, it appears as though the function is interrupted each time a value is returned. The function then picks up from where it left off the next time a value is requested. Behind the scenes, this is done by turning the function into a class with an internal state machine. A decompilation of the class reveals the somewhat extensive bookkeeping needed to pull this off.

Visual Basic's Iterators, look more like an anonymous function. The IEnumerable function will generally begin with a "Return Iterator" block, which is a special case of VB's new anonymous, multi-line function syntax. From within this block one may make calls to Return and Return Each.

A Return statement within an anonymous Iterator works just like C#'s yield return. The "yield" keyword is not needed because it is implied by the context.

A Return Each statement effectively "unwraps" a collection, returning the values one at a time.

VB's syntax has some advantages over the C# version. Since it is implemented as an anonymous function within another function, one could do some preliminary checks and calculations before creating the iterator. It would not be out of line to find multiple iterator implementations in one method, the specific one returned being determined at runtime.

One could also foresee custom iterators being created and used entirely within the scope of a function. This would be especially useful when turning an arbitrary data structure into something that can be operated on via the LINQ query notation.

No comments

Watch Thread Reply

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.