Visual Basic for Applications is not Haskell.

Apr 16, 2008 11:09

I find it difficult to describe the impedance mismatch experience when going from full time Haskell coding to writing Visual Basic for Applications. My first attempt involved trying to get higher order functions in VBA. My second attempt involved trying to do Python-style runtime creation of variables. VBA does not support any of the many things I tried.

Ouch, VBA is eating my sanity!

The most entertaining discovery so far is that vba in excel 2007 has separate keywords for code with side-effects, function does not have side-effects and can return a value, sub can have side-effects and cannot return a value.

visual basic, programming, vba

Previous post Next post
Up