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.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
What should Lambda Expressions in Visual Basic Look Like?
Posted by Jonathan Allen on Dec 12, 2006
In order to support LINQ, Visual Basic is adding support for lambda expressions. Lambda expressions are essentially inline functions and are a corner-stone of functional programming languages like Lisp and Haskell. As the next version of Visual Basic edges ever closer, certain syntactical issues need to be addressed.
On Friday, Paul Vick of Microsoft asked developers what syntax they want for this new capability. He presented three options.
The first is a very concise, C#-like syntax.
1: C#-style, "x => x + 1"
The second is more verbose, but also makes it clear that an in-line function is being used.
2: VB-style, "Function(x) x + 1"
Finally there is a mixed style that uses a backslash, because it resembles a lambda, and C#'s => notation.
3: Hybrid-style, "\x => x + 1"
DiegoV has proposed a fourth syntax with some interesting characteristics. It uses the parameter binding operator (:=) and the parameter's name.
4: bar(x):=x+1
Surprisingly #2 seems to be getting the majority of the support right now. As Sriram Krishnan says,
Definitely #2 - one of the things I loved in VB was that I didn't have to rack my heads as to what a cryptic character meant - which I had to do often in Perl
RelatedVendorContent
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Agility at scale, become as agile as you can be
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
No comments
Watch Thread Reply