Value Oriented Programming Part V: Return of the Values
Last year was "Value Oriented Programming Part 1: Functions".
But it would feel odd if the Value part of Value-Oriented Programming was called "Part 2". Surely Values should have been Part 1?
Why not both? Could they each be labelled Part 1? Values and Functions equally important?
Or maybe Values should be Part 0?
Then I thought "just call it Part X and decide later", and then - well why not V for Value, and then of course! Episode V: Return of the Values. It makes so much sense!
With functions covered last year, this year we will look at how making some of (most of!?) your types behave more like "values" than "objects" (with an explanation of what those mean) can improve code readability, correctness, maintainability, testability, and maybe even performance.
P.S. yeah, I know, the episode number should be VI.
Tony Van Eerd
Tony has been coding for well over 25 years, and hopefully coding well for most of that. Previously at Inscriber, Adobe, and BlackBerry, he now enables painting with light at Christie Digital. He is on the C++ Committee. He is a Ninja and a Jedi.