I have a collection of functions in a file kernel.r and right now I just source the file in when I want to use those functions. I was wondering if it would make sense to turn kernel.r into a package. If so, what is the advantage over sourcing it in? I couldn't find detailed info in the docs (Venables's tutorial or in the R help--I looked up library()) for creating a package. Thanks very much for any help. Bill Simpson -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
If you are actually working on the code you may find sourcing is more convenient than a package/library. Once the code is stable then putting it in a library has a few advantages, especially if there are a large number of functions and others are using them too: - ls() doesn't show functions in the library (so it is easier to see the stuff you are working on. -You shouldn't get multiple copies of the library functions in your .Rdata files. -If you fix something in the library then it is fixed wherever you or anyone else uses it. If you are sourcing it then you have not fixed copies saved in .RData files. [ Note: If you break something in the library then it is broken wherever you or anyone else uses it.] Paul Gilbert -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._