"... wonton (as in "users will change my variables this way") use of
that operator will inevitably lead to surprises and puzzlement later.
"
Is this related to the myriad of choices in a Chinese menu? ;-)
(The spelling is "wanton" -- ah the joys of English!)
Cheers,
Bert
Bert Gunter
"The tro
Jeff
Thanks for your insights. I suspected that this was the case but I was hoping
for a work-around. Regardless, I have modified the code so that the source()
command is no longer in a function — all the pre- and post-commands are now in
two functions, executed before and after the source co
I think you have boxed yourself into a corner, much like someone painting
the floor and failing to work their way toward an exit.
The whole premise that you will call "unknown code" that does "unknown
things" that change the global environment is a maintenance disaster. Give
up on at least one
R 3.2.4
OS X and Windows
Colleagues,
I distribute some code to co-workers and I am trying to simplify their task.
The issue is as follows:
1. The code automates an extensive set of processes. Many of the steps are
standardized. However, some of the steps may require that users write snippe
4 matches
Mail list logo
