Exercises in Programming Style–Closed Maps

NOTE : read the rest of the series, or check out the source code.

If you enjoy read­ing these exer­cises then please buy Crista’s book to sup­port her work.

exercises-prog-styles-cover

Fol­low­ing on from the last post, we will look at the Closed Maps style today.

 

Style 12 – Closed Maps

Constraints

  • Larger problem is decomposed into things that make sense for the problem domain
  • Each thing is a map from keys to values, some values are procedures/functions
  • The procedures/functions close on the map itself by referring to its slots

Does the constraints sound a bit like Javascript? It should, because this style is also known as prototypes.

 

First, let’s define what a Map constitutes to in our solution and the three things we need:

Style12_01

Then let’s add to the dataStorageObj map (this is analogous to the DataStorageManager in the Things and Letterbox styles). Here we’ll map the “init” key to a function that extracts the words from the specified path and stores the result as a string[] in the “data” key.

Style12_02

Next, let’s do the same for the stopWordsObj map:

Style12_03

and the wordFreqsObj map:

Style12_04

Finally, we need to initialize both dataStorageObj and stopWordsObj maps (notice that we need to first cast each value to a function signature and then invoke it with an argument, pretty ugly…):

Style12_05

and then count anything that’s not a stop word, and print the top 25:

Style12_06

These last couple of lines should be encapsulated into another map that’s analogous to the WordFrequencyController in the Things style. The reason I didn’t do this was because I wanted to stay faithful to Crista’s example where she chose not to for some reason.

 

Whilst this was another interest twist to the OOP paradigm that we (as .Net developers) are used to, like the Letterbox style it’s also very much at odds with how one would idiomatically approach thing in F#. As a style, we also didn’t get a chance to explore other possibilities that often come with this style – namely prototypal inheritance and monkey patching.

 

You can find the source code for this exer­cise here.

1 Comment

  1. Pingback: F# Weekly #2-#3, 2016 | Sergey Tihon's Blog

Leave a Reply

Your email address will not be published.