In my last post I have discussed how to work around GNU R scoping rules using environment function. This time let us look at a practical example using recode function from car package.
First let us look at how recode works:
transforms 1 23 12 3 into “a” “2” “3” “a” “2” “3”. In further codes we will want to replicate this result using several different approaches sticking to the same definition of variable x.
Interestingly the string recodes is split and evaluated inside recode function so we can use the following code to get the same result:
Now we can change b variable to get different recoding results without the change of recode call. Note that this use of recode is not following its help page as documentation not support using variables inside recodes string.
Let us now try writing a simple wrapper around recode that does the same stuff. Unfortunately:
does not work and produces error. Due to lexical used in GNU R from and to variables are not within recode function scope.
Here are two ways to work around it:
The first function recode.one moves recode into its own lexical scope. Unfortunately it also has to move squeezeBlanks function into its scope to work properly as recode calls it. To avoid this recode.one2 is put into environment(recode) environment so squeezeBlanks will be in its lexical scope.
Those examples helped me better understand how scoping works in GNU R, but they are dangerous. To see this one can look at the following code:
Another lesson that one has to be careful when hacking in GNU R.