Open GoogleCodeExporter opened 9 years ago
Yes, I can see this is going to be a problem in the longer term.
As an interim solution, I would recommend using status="new" in the Rput
command, or set the RFortran global variable, statusDef = "new"
This checks if an Rput command is going to overwrite an existing R variable and
returns an error. At least then an error is returned if a variable is going to
be overwritten.
In the longer term R has a feature called an "environment", where an R variable
can be defined in a an environment and does not interact with other variables
in a different environment. The R scoping rules are hard to follow however -
see http://cran.r-project.org/doc/contrib/Fox-Companion/appendix-scope.pdf
An Rcall command could first setup its own environment, perform its
calculations return the values and somehow close the environment.
Something to look at in longer term
Original comment by mark.th...@gmail.com
on 13 Jun 2011 at 11:55
Original issue reported on code.google.com by
dmitri.k...@gmail.com
on 13 Jun 2011 at 9:53