[Rd] problem reported in 00check.log-package not found

2011-01-12 Thread carol white
I set setenv R_LIBS path_to_local_Rpackages still I get the error message that a package not found Warning in library(pkg, character.only = TRUE, logical.return = TRUE, lib.loc = lib.loc) : there is no package called 'prodlim' Error : package 'prodlim' could not be loaded ERROR: lazy loading

[Rd] Access R Help Content From R

2011-01-12 Thread Roebuck,Paul L
Have UI that simplifies running code from another (internal) package, allowing user to set values on fields I basically grabbed from results of calls to formals() for various functions. That works fine for the most part. But it was requested to investigate some type of popup help or something for e

Re: [Rd] as.environment.list provides inconsistent results under torture

2011-01-12 Thread luke-tierney
On Wed, 12 Jan 2011, peter dalgaard wrote: On Jan 12, 2011, at 14:18 , wrote: I did do a quick scan of R-devel for this issue with eval and found these: ./unix/aqua.c: eval(LCONS(install("library"),CONS(install("grDevices"),R_NilValue)),R_GlobalEnv); ./unix/sys-std.c:

Re: [Rd] as.environment.list provides inconsistent results under torture

2011-01-12 Thread peter dalgaard
On Jan 12, 2011, at 14:18 , wrote: > > I did do a quick scan of R-devel for this issue with eval and found these: > >./unix/aqua.c: > eval(LCONS(install("library"),CONS(install("grDevices"),R_NilValue)),R_GlobalEnv); >./unix/sys-std.c:infile = PROTECT(eval(lang1(RComp_ge

Re: [Rd] as.environment.list provides inconsistent results under torture

2011-01-12 Thread luke-tierney
On Tue, 11 Jan 2011, Simon Urbanek wrote: On Jan 11, 2011, at 6:55 PM, wrote: No. Lots of internal functions expect their callers to protect their arguments, for efficiency reasons. eval is called very often and almost always with argument that are protected because they are in the evalu

Re: [Rd] as.environment.list provides inconsistent results under torture

2011-01-12 Thread Duncan Murdoch
On 11-01-11 6:55 PM, luke-tier...@uiowa.edu wrote: No. Lots of internal functions expect their callers to protect their arguments, for efficiency reasons. eval is called very often and almost always with argument that are protected because they are in the evaluation engine, so it would be wastefu