> The shell command > R CMD something > currently acts as though it puts R_HOME/bin on the front > of PATH, looks for an executable file called 'something' > in PATH, and then executes it. The executable may call R > or it may not. > > I think that running an R script file is sufficiently different > from running an executable file that the operation should > not also be called 'CMD'.
Fair enough. But it would still be extremely useful to have an R "command" which did run R scripts (which naively you would expect R CMD to do do). Maybe R SCRIPT ? Or R CMD package::script could look for an arbitrary script and execute it - I suspect this would be trickier cross-platform though. One could also consider eliminating R CMD and the bin directory, given that most of the scripts there now just call an R function. Perhaps a general syntax for calling R scripts in an package could subsume these important scripts in a consistent and package-extensible manner. Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
