Just read an article from Yihui’s blog in which he recommends a lot using
library() instead of
require() to attach/load a package .
So I wonder how does the source code of
require() look like.
The source code pops up and shows that it’s mainly about how to deal with the arguments using
else control flow and
There are 3 kinds of output:
- TRUE - successfully load a package or the package if already loaded;
- Warning message and FALSE - can’t allocate the package;
- Error message and FALSE - find the package but can’t load it.
What’s tricky is when there is no such package, you will not find it out until the code try to access this package. Try this:
## Error in library(abcd): there is no package called 'abcd'
## Loading required package: abcd ## Warning in library(package, lib.loc = lib.loc, character.only = TRUE, ## logical.return = TRUE, : there is no package called 'abcd'
There is no package called “abcd”,
library(abcd) throws an error message which stops the process while
require(abcd) just generates a warning message. That doesn’t halt the program at all.
Searching for An Attached Package
library() tell you whether a package is already attached? No. But this function returns a logical value telling you if the “load” action is successfully executed.
So another big difference between the 2 functions is
require() can tell you the status of a package - if it is already attached - before it runs the “load” action (yes, using exactly the
How does the
require() search for a attached package? In the source code, we can see that:
search() gives a list of attached packages. Don’t mix it with
installed.packages() which gives, apprently, the list of installed packages. For example, in my PC, the
dplyr package is already installed but not attached:
##  TRUE
##  FALSE
##  TRUE
This gives you an alternative way to see if a package is loaded or not.
Double Colon Operator
Another simple way to use the functions from a package is using
:: operator. This operator returns the function from package even you didn’t load it. Compare the 2 chunks below:
## Error in eval(expr, envir, enclos): could not find function "summarise"
## Source: local data frame [3 x 3] ## ## cyl avg_mpg avg_wt ## (dbl) (dbl) (dbl) ## 1 4 26.66364 2.285727 ## 2 6 19.74286 3.117143 ## 3 8 15.10000 3.999214
When should we use
::? It depends on the context.
- Is there any function masked by the lately loaded package? Do you need to use them?
- Does the program frequently use those functions? Do you want to code like
library(dplyr)or you can stand adding
There is also an operator
:::, help yourself to figure it out (I don’t use it, for now).
Detaching A Package
Now comes the question: how to detach a package?
## Attaching package: 'dplyr' ## ## The following objects are masked from 'package:stats': ## ## filter, lag ## ## The following objects are masked from 'package:base': ## ## intersect, setdiff, setequal, union
##  FALSE