sourceTo() in R.utils will allow you to source() a file into an environment.

/Henrik

On 1/9/07, Gabor Grothendieck <[EMAIL PROTECTED]> wrote:
> Try this:
>
> > e <- new.env()
> > e$f <- function(x)x
> > attach(e)
> > search()
>  [1] ".GlobalEnv"        "e"                 "package:stats"
>  [4] "package:graphics"  "package:grDevices" "package:utils"
>  [7] "package:datasets"  "package:methods"   "Autoloads"
> [10] "package:base"
> > f
> function(x)x
>
> On 1/8/07, Tong Wang <[EMAIL PROTECTED]> wrote:
> > Hi  all,
> >
> > I created environment  "mytoolbox" by :   mytoolbox <- 
> > new.env(parent=baseenv())
> > Is there anyway I put it in the search path ?
> >
> > If you need some background :
> >  In a project, I often write some small functions,  and load them into my 
> > workspace directly,   so when I list the objects
> >  with ls(), it looks pretty messy.  So I am wondering if it is possible to 
> > creat an environment,  and put these tools into
> >  this environment.  For example,  I have functions    fun1(), fun2() ...... 
> >    and creat an environment  mytoolbox  which
> >  contains all these functions.  And it should be somewhere in the search 
> > path:   ".GlobalEnv"        "mytoolbox"                        
> > "package:methods"  ........
> >
> > ______________________________________________
> > R-help@stat.math.ethz.ch mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-help
> > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> > and provide commented, minimal, self-contained, reproducible code.
> >
>
> ______________________________________________
> R-help@stat.math.ethz.ch mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>

______________________________________________
R-help@stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Reply via email to